Develop Bugs

HTC one M8 Wifi problems please help.

My phone wont turn on wifi. I tried factory reset multiple times. nothing is working. help.

233AK said:
My phone wont turn on wifi. I tried factory reset multiple times. nothing is working. help.
Click to expand...
Click to collapse
Did you flash any roms or make any other changes to your phone ?

clsA said:
Did you flash any roms or make any other changes to your phone ?
Click to expand...
Click to collapse
yeah im using the Android Revolution HD rom.

Wild guess: you are on latest ARHD and you didn't update your firmware to 3.28.401.x, aren't you

Lol, we really need a sticky or something for the latest update. Or the ROM devs need to include a warning. (Not that im saying its any of their responsibility)

bloodhawk said:
Lol, we really need a sticky or something for the latest update. Or the ROM devs need to include a warning. (Not that im saying its any of their responsibility)
Click to expand...
Click to collapse
Not going to help mate, the people don't bother to read, that's the problem.
All the developers can put a warning in THIS BIG and the majority of the people will still scroll past it to just download the ROM in their rush to be "cool hackerz"
There is plenty enough proof of that already, developers clearly state in RED in their first post, THIS WILL NOT WORK WITH VERIZON and within the first 10 replies an idiot will come out and ask "Will this work with Verizon?"

Always read the last several pages on any rom you flash. You will always see any current issues or hot topics that way.
Read read read. That's a requirement for this hobby. ?

update post. I switched roms and still having the same problems. I'm using venom now.

KJ said:
Always read the last several pages on any rom you flash. You will always see any current issues or hot topics that way.
Read read read. That's a requirement for this hobby. ?
Click to expand...
Click to collapse
First 2 pages and last 3 is a must definitely! :good:
---------- Post added at 06:03 AM ---------- Previous post was at 06:01 AM ----------
233AK said:
update post. I switched roms and still having the same problems. I'm using venom now.
Click to expand...
Click to collapse
What version of venom?

233AK said:
update post. I switched roms and still having the same problems. I'm using venom now.
Click to expand...
Click to collapse
Ok first thing, goto the bootloader and check what the OS field says. If it is anything under 3.XX.XXX.X, then your need to update your firmware. Otherwise the problem is something else.

bloodhawk said:
Ok first thing, goto the bootloader and check what the OS field says. If it is anything under 3.XX.XXX.X, then your need to update your firmware. Otherwise the problem is something else.
Click to expand...
Click to collapse
Won't it give the OS version for the ROM he has on which might be 3.x anyways?
I also think it's outdated firmware on his part, radio firmware needs to be updated in order for data, mobile, wifi, bluetooth etc to function properly. This guy can't be bothered so I don't know why we bother either.
ARHD - 10 to 1 he used 21.0
Venom - 10 to 1 it's 3.0
But we should guess these things because he doesn't answer anyone when asked. What version was he on before? Most likely a 2.x but we won't know that either because
He didn't take note of it before he flashed away
He doesn't want to make the effort
It's easier to just expect others to do everything for you.

BerndM14 said:
Won't it give the OS version for the ROM he has on which might be 3.x anyways?
I also think it's outdated firmware on his part, radio firmware needs to be updated in order for data, mobile, wifi, bluetooth etc to function properly. This guy can't be bothered so I don't know why we bother either.
ARHD - 10 to 1 he used 21.0
Venom - 10 to 1 it's 3.0
But we should guess these things because he doesn't answer anyone when asked. What version was he on before? Most likely a 2.x but we won't know that either because
He didn't take note of it before he flashed away
He doesn't want to make the effort
It's easier to just expect others to do everything for you.
Click to expand...
Click to collapse
:cyclops:
I think when i flashed IC 5.0.0 without updating the firmware, my OS version still said 2.XX.XXX.X.Though It is as you say the radio firmwares need to be updated.
Changed to the new one once i flashed the update.
But yeah, you'r right, not many people willing to search the forums. The same issue has been discussed at least 20 times now. With 5 threads on the 2-3 pages of the Q&A section. I found my solution within maybe 2 mins and after reading less than 2 pages of the ROM i was updating. to.

bloodhawk said:
:cyclops:
I think when i flashed IC 5.0.0 without updating the firmware, my OS version still said 2.XX.XXX.X.Though It is as you say the radio firmwares need to be updated.
Changed to the new one once i flashed the update.
But yeah, you'r right, not many people willing to search the forums. The same issue has been discussed at least 20 times now. With 5 threads on the 2-3 pages of the Q&A section. I found my solution within maybe 2 mins and after reading less than 2 pages of the ROM i was updating. to.
Click to expand...
Click to collapse
Oh ok, I thought maybe it took that information from the build as well which would show the ROM's version(3.28.401.7) kinda like doing a getprop
I only flashed a custom ROM once and honestly, didn't even have a look at the OS in bootloader and even if I did happen to look at it the version probably wouldn't have shown what we're looking for now(I was updated to latest firmware so didn't have issues)

BerndM14 said:
Oh ok, I thought maybe it took that information from the build as well which would show the ROM's version(3.28.401.7) kinda like doing a getprop
I only flashed a custom ROM once and honestly, didn't even have a look at the OS in bootloader and even if I did happen to look at it the version probably wouldn't have shown what we're looking for now(I was updated to latest firmware so didn't have issues)
Click to expand...
Click to collapse
The bootloader pulls it probably from the hardware chip or something and then matches, if it doesn't, it shows up in RED. I could be wrong though.
Getprop pulls it from a .ro file on one of the partitions.
I had a massive heart attack when i first got the phone though. Couldn't unlock the bootloader as well since some partition detail was messed up. Talked to some Dev at HTC, and a day later a very convenient 'GPS' OTA shows up and all is good after that. But before i contacted HTC, i thought maybe flashing over some OTA is gonna sort it for me, the phone was on 2.22.1540.4 and i flashed over the 2.22.1540.3 OTA. Was stuck in RUU flash mode for a few hours and couldn't find anything on the forums, the only way to boot the phone was to use fastboot oem boot string. But it would get stuck in the RUU mode after every restart. That is when i noticed the differences on what the OS field says.
Once the correct OTA was flashed all was golden.
Im now waiting for the Dev edition or GPE to get Lollipop and im gonna convert to that SKU.

bloodhawk said:
The bootloader pulls it probably from the hardware chip or something and then matches, if it doesn't, it shows up in RED. I could be wrong though.
Getprop pulls it from a .ro file on one of the partitions.
I had a massive heart attack when i first got the phone though. Couldn't unlock the bootloader as well since some partition detail was messed up. Talked to some Dev at HTC, and a day later a very convenient 'GPS' OTA shows up and all is good after that. But before i contacted HTC, i thought maybe flashing over some OTA is gonna sort it for me, the phone was on 2.22.1540.4 and i flashed over the 2.22.1540.3 OTA. Was stuck in RUU flash mode for a few hours and couldn't find anything on the forums, the only way to boot the phone was to use fastboot oem boot string. But it would get stuck in the RUU mode after every restart. That is when i noticed the differences on what the OS field says.
Once the correct OTA was flashed all was golden.
Im now waiting for the Dev edition or GPE to get Lollipop and im gonna convert to that SKU.
Click to expand...
Click to collapse
Yeah perhaps it does get it from boot.img or something similar, even then the new ROM flashed already contains those version numbers so I just figured it'll show the ROMs number and not the old OS version. Either way... It's cool. Like I said I never actually bothered to look at the OS Version there when I flashed Venom, had it on for 2 days and went back to stock(converted to Dev Edition).
GPE Will no doubt have it faster but I don't want to convert to GPE. Personally I'm not a major fan of "vanilla android". I actually like Sense. So hopefully it won't be too long after GPE gets the update that it'll roll out for Dev Edition.
That said, I'll probably do the exact opposite of what I just said and convert to GPE anyways just to see what Lollipop is like

BerndM14 said:
Yeah perhaps it does get it from boot.img or something similar, even then the new ROM flashed already contains those version numbers so I just figured it'll show the ROMs number and not the old OS version. Either way... It's cool. Like I said I never actually bothered to look at the OS Version there when I flashed Venom, had it on for 2 days and went back to stock(converted to Dev Edition).
GPE Will no doubt have it faster but I don't want to convert to GPE. Personally I'm not a major fan of "vanilla android". I actually like Sense. So hopefully it won't be too long after GPE gets the update that it'll roll out for Dev Edition.
That said, I'll probably do the exact opposite of what I just said and convert to GPE anyways just to see what Lollipop is like
Click to expand...
Click to collapse
Big sense fan here myself.. But cant wait for thr sense update. Let's see how fast they do it.
In the mean time hope the OP UPDATED his firmware.

bloodhawk said:
Big sense fan here myself.. But cant wait for thr sense update. Let's see how fast they do it.
In the mean time hope the OP UPDATED his firmware.
Click to expand...
Click to collapse
:laugh: I was just thinking that... yet somehow I doubt it, next post will probably be to ask how he does that.
Oh well, we should probably stop high jacking his thread even though he started it and doesn't say anything in it himself.

I've never seen so many people not read the threads before blindly flashing things, seriously.
{
"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"
}

Why bother unlocking and rooting?

Hi,
Please help me understand why I would bother unlocking and rooting my Pixel XL when there isn't an custom recoveries available thus no options for custom roms.
In the past I've always rooted for custom roms and especially for the option to use my hot spot on my unlimited data plan.
Is everyone basically just waiting for custom recovery to become available?
I'm just trying to figure out if I should bother unlocking and rooting now or if I should wait for custom recovery.
and please, if I have no idea what i'm talking about please correct me.
I never thought I would see the day a google phone would come with a locked bootloader regardless of who the vendor it.
Thanks
Ken

Kc0r8y said:
Hi,
Please help me understand why I would bother unlocking and rooting my Pixel XL when there isn't an custom recoveries available thus no options for custom roms.
In the past I've always rooted for custom roms and especially for the option to use my hot spot on my unlimited data plan.
Is everyone basically just waiting for custom recovery to become available?
I'm just trying to figure out if I should bother unlocking and rooting now or if I should wait for custom recovery.
and please, if I have no idea what i'm talking about please correct me.
I never thought I would see the day a google phone would come with a locked bootloader regardless of who the vendor it.
Thanks
Ken
Click to expand...
Click to collapse
It's simple, there's still root and many other editions that can be done with an unlocked bootloader and root. If you want details by details then you should do some research. Maybe drop by the themes and app section

TechBSwift said:
It's simple, there's still root and many other editions that can be done with an unlocked bootloader and root. If you want details by details then you should do some research. Maybe drop by the themes and app section
Click to expand...
Click to collapse
No, I'm not looking for detail, by detail. I'm just asking high level, what is the benefit of an unlocked bootloader and root without custom recovery. At this point is it just a few custom apps?

Actually I'm pretty sure it makes him the coolest cat in town ?

Even if nothing else I'll root just to be able to switch to IOS emojis from those godawful Android emojis. But once recoveries and ROMs come out I'll be back to being a flashaholic.

Kc0r8y said:
Hi,
Please help me understand why I would bother unlocking and rooting my Pixel XL when there isn't an custom recoveries available thus no options for custom roms.
In the past I've always rooted for custom roms and especially for the option to use my hot spot on my unlimited data plan.
Is everyone basically just waiting for custom recovery to become available?
I'm just trying to figure out if I should bother unlocking and rooting now or if I should wait for custom recovery.
and please, if I have no idea what i'm talking about please correct me.
I never thought I would see the day a google phone would come with a locked bootloader regardless of who the vendor it.
Thanks
Ken
Click to expand...
Click to collapse
Custom kernal (elementalX) that enables amongst other things ...
Swipe to wake / sleep feature
High brightness mode .... Excellent when outdoors
Root... Gives ability to use apps that otherwise don't work, eg skvolex Call recorder

Thank you everyone. I really appreciate the explanation.

Don't forget that if you don't unlock your bootloader now, assuming you are on VZW, you may (most likely) not be able to do so in the future. I didn't want to trust that I could postpone an update (even with auto update turned off), so I unlocked my bootloader. In fact, as I was unlocking, my phone automatically took the first update when it rebooted during my first attempt to unlock the bootloader - even though I had auto update turned off.
I have 3 main desires to change on the phone:
- run custom kernel with swipe to unlock/lock
- enable tethering
- keep Android Pay available.
For now, I have flashed a kernel does swipe to unlock, along with enabling Android Pay while maintaining an unlocked bootloader, and not flashing root. I haven't needed to root to get tethering because of the network switching workaround.
I recognize I'm probably fighting a losing battle, though. Android Pay will probably be patched to recognize unlocked bootloader. And there's a possibility that VZW will adapt its tethering detection to disable the workaround.

jasoraso said:
Don't forget that if you don't unlock your bootloader now, assuming you are on VZW, you may (most likely) not be able to do so in the future. I didn't want to trust that I could postpone an update (even with auto update turned off), so I unlocked my bootloader. In fact, as I was unlocking, my phone automatically took the first update when it rebooted during my first attempt to unlock the bootloader - even though I had auto update turned off.
I have 3 main desires to change on the phone:
- run custom kernel with swipe to unlock/lock
- enable tethering
- keep Android Pay available.
For now, I have flashed a kernel does swipe to unlock, along with enabling Android Pay while maintaining an unlocked bootloader, and not flashing root. I haven't needed to root to get tethering because of the network switching workaround.
I recognize I'm probably fighting a losing battle, though. Android Pay will probably be patched to recognize unlocked bootloader. And there's a possibility that VZW will adapt its tethering detection to disable the workaround.
Click to expand...
Click to collapse
You could always root your phone, add the build.prop setting, and then unroot.

skaforey said:
You could always root your phone, add the build.prop setting, and then unroot.
Click to expand...
Click to collapse
Thanks! As I was typing my reply, I actually thought about doing that. Perhaps the next elemntal kernel update, I'll do that. I don't often tether - usually its when I'm in the car with my kids on a trip and they want to stream some netflix to their chromebooks, and I'm usually driving, and trying to get my wife to do the network switching workaround while I'm driving will be a challenge.

wolfu11 said:
I haven't been impressed with a custom rom in a long time.
Click to expand...
Click to collapse
Same here dude...same here. Towards the end of KitKat was an amazing time for ROMs especially when talking about Slim ROMs and Paranoid Android. I haven't even rooted anything since Lollipop. I just don't have a need for it anymore.

I'll give you an obvious reason to unlock your bootloader right now.
If you wait too long and the exploits are patched out (which google apparently said they will be) then when custom recovery is released for Pixel XL you probably SOL.
If you sit there for a while refusing update waiting for TWRP, why not root now and disable the update notification?
And mods are already out. Look at my notification bar.
{
"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"
}
Sent from my Pixel XL using Tapatalk

skaforey said:
You could always root your phone, add the build.prop setting, and then unroot.
Click to expand...
Click to collapse
I thought that once you unroot, then reboot, build.prop will get overwritten and all your changes will be lost. I am looking to do this for enabling wireless display as well.

Ambient Display
Audio Mods
Touch to wake
Sleep to wake
Camera Mods
Emojis
Themes
Kernels
Just to name a few off the top of my head. I am only on day 1 with pixel but if i keep it will get rooted/rommed and modded. Take full advantage of an unlocked phone. No point in getting if you just use like a normal device imo

oneandroidnut said:
Ambient Display
Audio Mods
Touch to wake
Sleep to wake
Camera Mods
Emojis
Themes
Kernels
Just to name a few off the top of my head. I am only on day 1 with pixel but if i keep it will get rooted/rommed and modded. Take full advantage of an unlocked phone. No point in getting if you just use like a normal device imo
Click to expand...
Click to collapse
Thanks for your feedback! I am now unlocked and rooted!

marcjc said:
I thought that once you unroot, then reboot, build.prop will get overwritten and all your changes will be lost. I am looking to do this for enabling wireless display as well.
Click to expand...
Click to collapse
Just to update anyone who may be interested. I rooted, made my changes, then unrooted, rebooted a whole bunch of times and my changes survived unrooting and rebooting.

Kc0r8y said:
Thanks for your feedback! I am now unlocked and rooted!
Click to expand...
Click to collapse
Don't forget custom kernels to increase the speed of the 821 CPU. Out of the box, the CPU is clocked down to the 820 level. With a little over clocking we can experience the full potential of the 821.

Thread cleaned.
Folks, keep the thread on topic and post in accordance with the forum rules you agreed to when you joined XDA.
Cheers,
Magnum_Enforcer
FSM

I NEED Redmi Note 8 Pro firmware v11.0.7.0 PGGMIXM Can Anyone Help?

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

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.

Question Any app i can use to root my samsung a54 5g?

Mentioned above is my question. Thank you

joining in on this question cause my new phone is on the way. are there any working custom recoverys or custom roms available yet? lineage os and twrp seems to have nothing yet.
i've seen a bootloader unlock on yt but found nothing to push onto the device afterwards

Depends as far as I've seen on mine the oem unlock is not it the settings under developer options so no bootloader unlocking which means no root even though it's exynos

{
"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"
}
The option is in developer settings

Why put something different on for the sake of only having sth different? Cant see where any custom rom could be any better than Samsungs current ONE UI, which is great.

download magisk apk on your a54 and again download your a54's firmware from samfw.com, unpack it and get your AP file, open magisk and click install and select from file and select AP file, make sure your bootloader is unlocked, move your patched AP file to your WINDOWS PC, install samsung usb drivers and odin https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/, open odin and connect your a54 to your pc with a usb cable, now put the patched AP into the AP slot of course and hit start, after it flashes you will have a rooted a54.

dj_mol3y_x8 said:
View attachment 5887405
The option is in developer settings
Click to expand...
Click to collapse
Werid not in mine

jolly_roger_hook said:
Werid not in mine
Click to expand...
Click to collapse
what model do you got? for example i got a a53 and its model is A536B which means it OEM unlockable

TringQuack said:
what model do you got? for example i got a a53 and its model is A536B which means it OEM unlockable
Click to expand...
Click to collapse
A546B/DS

terry_mccann said:
Why put something different on for the sake of only having sth different? Cant see where any custom rom could be any better than Samsungs current ONE UI, which is great.
Click to expand...
Click to collapse
Fully agree with you.
oneUI is not anything like touchwiz from back in the day.
oneUI is far more optimized and getting less bloated and much more freedom.
So for me it's Samsung's stock OS or a buggy rom. No real choice
Let's do a run down over the years
Early android years CM/linage was where it was at
Reasons...
More customizable.
Less bloat
Theme's
Add or remove apps/features
Early Samsung
Touchwiz bloat apps none removable
Horrible UI
Slow and laggy
Now if we move to modern Samsung things are much different
90% of pre installed apps are removable
Theme's as standard. And can use apps like theme park and hex installer to side load themes created. oneUI only core (no root needed). Not possible oneUI CORE
Regular updates
Fast and streamline.
Samsung have listened to its users and are definitely heading in the correct direction.
So that said for me I don't get the need for a custom OS.
I will just use Sammy OS with a theme I make for the looks I want

dj_mol3y_x8 said:
Fully agree with you.
oneUI is not anything like touchwiz from back in the day.
oneUI is far more optimized and getting less bloated and much more freedom.
So for me it's Samsung's stock OS or a buggy rom. No real choice
Let's do a run down over the years
Early android years CM/linage was where it was at
Reasons...
More customizable.
Less bloat
Theme's
Add or remove apps/features
Early Samsung
Touchwiz bloat apps none removable
Horrible UI
Slow and laggy
Now if we move to modern Samsung things are much different
90% of pre installed apps are removable
Theme's as standard. And can use apps like theme park and hex installer to side load themes created. oneUI only core (no root needed). Not possible oneUI CORE
Regular updates
Fast and streamline.
Samsung have listened to its users and are definitely heading in the correct direction.
So that said for me I don't get the need for a custom OS.
I will just use Sammy OS with a theme I make for the looks I want
Click to expand...
Click to collapse
to put it simple: updates
for example on my current lineageOS i get a systemupdate every half month, they are very up to date. or even have higher android-support past the manufacturers "expiration date". and i still dont see any big company names supporting android updates past the shelflife, except nokia and their longtime support promise, which gets also dropped after 4 years, while the hardware could still support newer androids. i would have been stuck on android 10 with my current device (oneplus5) but here i am with a smooth android 13 on lineageOS. thats the main reason i want a custom rom and dont stay on stock.
apps will have higher android requirements and my phone will just get outdated by the playstore - wow.

dj_mol3y_x8 said:
Fully agree with you.
oneUI is not anything like touchwiz from back in the day.
oneUI is far more optimized and getting less bloated and much more freedom.
So for me it's Samsung's stock OS or a buggy rom. No real choice
Let's do a run down over the years
Early android years CM/linage was where it was at
Reasons...
More customizable.
Less bloat
Theme's
Add or remove apps/features
Early Samsung
Touchwiz bloat apps none removable
Horrible UI
Slow and laggy
Now if we move to modern Samsung things are much different
90% of pre installed apps are removable
Theme's as standard. And can use apps like theme park and hex installer to side load themes created. oneUI only core (no root needed). Not possible oneUI CORE
Regular updates
Fast and streamline.
Samsung have listened to its users and are definitely heading in the correct direction.
So that said for me I don't get the need for a custom OS.
I will just use Sammy OS with a theme I make for the looks I want
Click to expand...
Click to collapse
Not really that I want a custom rom there are a good deal of things root can be used for that doesn't involve a custom rom such as full access to all storage areas on the phone, custom recovery (TWRP). Samsung removed access to alot of minor some major things that were what made android great to stay current with the market root allows you to get some back I do agree with UI being way better then touchwiz I still want root for other things

Samsung U.S. variants don't have OEM Unlock option anymore. I have an S23 Ultra & an A54 - both are US unlocked variants and neither of them have it. I mean I bought them unlocked, so why no OEM unlock? I don't personally care as custom ROM's never really act right. It's only good for old phones IMO that aren't updated any longer and to put Lineage OS on it or something.

mewcatchew said:
Samsung U.S. variants don't have OEM Unlock option anymore. I have an S23 Ultra & an A54 - both are US unlocked variants and neither of them have it. I mean I bought them unlocked, so why no OEM unlock? I don't personally care as custom ROM's never really act right. It's only good for old phones IMO that aren't updated any longer and to put Lineage OS on it or something.
Click to expand...
Click to collapse
Yea that's the same issue I have even though it's unlocked and exynos its US so they completly removed the oem option from dev settings

dj_mol3y_x8 said:
View attachment 5887405
The option is in developer settings
Click to expand...
Click to collapse
what model do you have?
i'm using a546u1 and it doesn't show oem unlocking in developer settings

Just putting this out there.
Reason I got into custom ROMs in the first place is because they're usually light-weight so they run faster and they don't come with a bunch of invasive and uninstallable bloat-ware. With my A546U I can't even uninstall MS OneDrive and it drives me nuts. Hoping someone figures out how to unlock the bootloader on this thing so I can flash the PE rom someone mentioned in another thread. I also saw there's a version of TWRP that's in the works. Hopefully someone smarter than myself can figure this out soon. Still probably gonna purchase a different phone because removing all the excessive google/Samsung apps is a necessity for me.
This is my first Samsung device and I'm not too thrilled with it tbh

h0miemaru said:
Just putting this out there.
Reason I got into custom ROMs in the first place is because they're usually light-weight so they run faster and they don't come with a bunch of invasive and uninstallable bloat-ware. With my A546U I can't even uninstall MS OneDrive and it drives me nuts. Hoping someone figures out how to unlock the bootloader on this thing so I can flash the PE rom someone mentioned in another thread. I also saw there's a version of TWRP that's in the works. Hopefully someone smarter than myself can figure this out soon. Still probably gonna purchase a different phone because removing all the excessive google/Samsung apps is a necessity for me.
This is my first Samsung device and I'm not too thrilled with it tbh
Click to expand...
Click to collapse
You can use ADBAppControl made by fellow XDA member to remove any un-uninstallable app through ADB.
There's no rescritctions with this program so be careful. You can disable/uninstall critical system apps and it won't stop you, (systemUI, OneUI Home, etc).
Can be used to completely de-google the phone, which is what i use it for.

FoxyDrew said:
You can use ADBAppControl made by fellow XDA member to remove any un-uninstallable app through ADB.
There's no rescritctions with this program so be careful. You can disable/uninstall critical system apps and it won't stop you, (systemUI, OneUI Home, etc).
Can be used to completely de-google the phone, which is what i use it for.
Click to expand...
Click to collapse
Awesome thank you so much!
Definitely going to look into this.
And just to clarify this can be done to the stock firmware A546U (US version; no OEM unlock toggle in dev settings)?