Develop Bugs

[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.

Is it possible to boot samsung firmware with CM bootloader

Hi, title is explaining all.
I need a bootloader for running custom p601 roms on my p602. CM12 bootloader works on my device, P601 bootloader does not. Is is possible to boot samsung firmwares with CM bootloader. ?
Thanks.

Any ideas ?

Any advice ? I don't want to brick my device

Bootloader? I think you mean recovery and no you will brick.

macrostr said:
Any advice ? I don't want to brick my device
Click to expand...
Click to collapse
Mate , the worst situation is that you mess up all the partitions which you can fix using the stock pit files ( for which I made a thread ... here ) ... so don't get frightened and try the recover and the ROM ( even in the recovery , you can't install the ROM because the model number differs ... ) also tell me about the nand structure and the CPU and also the Network support ... If everything is the same (esp the CPU and Nand Structure ) it's alright to give it a try but, if not , It's a waste of time to play this ... so , please provide a bit more detail ...
With Best Wishes
Hitman1376​

Hi guys, thanks for your response
Orion116 said:
Bootloader? I think you mean recovery and no you will brick.
Click to expand...
Click to collapse
Yes, I can install TWRP and flash custom p601 roms (5.0.1) without a problem. When I flash a 5.1.1 custom rom, it did not. I beleive it is because of the new boot.img of 5.1.1 roms.
hitman1376 said:
Mate , the worst situation is that you mess up all the partitions which you can fix using the stock pit files ( for which I made a thread ... here ) ... so don't get frightened and try the recover and the ROM ( even in the recovery , you can't install the ROM because the model number differs ... ) also tell me about the nand structure and the CPU and also the Network support ... If everything is the same (esp the CPU and Nand Structure ) it's alright to give it a try but, if not , It's a waste of time to play this ... so , please provide a bit more detail ...
With Best Wishes
Hitman1376​
Click to expand...
Click to collapse
It'is identical to SM-P601 variant of note 10.1^2014, Just the RIL part is modified for not to support voice calls, It only use sim to connect network. When I flash p601 roms, I am able to make voice calls. I also make thread about it here. Partitioning is differs from p601 too. It's not the same but similar. One of my friends overwrite the pit with p601 stock roms and bricked the device before. I can boot with cm12 and cm13 roms for p601. But I want to use 5.1.1 stock or stock based roms.

macrostr said:
Hi guys, thanks for your response
Yes, I can install TWRP and flash custom p601 roms (5.0.1) without a problem. When I flash a 5.1.1 custom rom, it did not. I beleive it is because of the new boot.img of 5.1.1 roms.
It'is identical to SM-P601 variant of note 10.1^2014, Just the RIL part is modified for not to support voice calls, It only use sim to connect network. When I flash p601 roms, I am able to make voice calls. I also make thread about it here. Partitioning is differs from p601 too. It's not the same but similar. One of my friends overwrite the pit with p601 stock roms and bricked the device before. I can boot with cm12 and cm13 roms for p601. But I want to use 5.1.1 stock or stock based roms.
Click to expand...
Click to collapse
So, if it's this way , give " Binh24 mod " stock 5.1.1 ROM a shot ... Happy Flashing ... :laugh:

hitman1376 said:
So, if it's this way , give " Binh24 mod " stock 5.1.1 ROM a shot ... Happy Flashing ... :laugh:
Click to expand...
Click to collapse
I flashed the binh24 mod, but not booted up, not even show samsung logo, just tried to boot and go back to recovery.

macrostr said:
I flashed the binh24 mod, but not booted up, not even show samsung logo, just tried to boot and go back to recovery.
Click to expand...
Click to collapse
You know why ? ( no that's not " Because sky is high !!! " ) the reason is that you have the KK Bootloader which causes the problem ... as you know , first you need to flash a P601 firmware to get the new bootloader ( Extremely Important Note !!!! ... Do not even think of ( ) ticking the " Update bootloader " in the Odin which makes you blame your self later ... !!!! the lollipop boot loader is installed by it self ... just do nothing about it ...) try if it get's installed that way ... also take a look at this ... maybe you find it useful ( to convert the P602 to P601 !!! ) Note that I haven't tried it on Lollipop CM or some other ROMs so make a backup first !!! ... If you couldn't install the Odin way , there are other apps and if they failed , then find the Multi-file version of P600 / P601 Lollipop ROM to flash the bootloader part directly ... Good luck :good:

hey dude have you ever found something about 5.1.1 bootloader for p602? I need that

I have restored my device which is a Samsung Galaxy Note 10.1 edition 2014 by using the settings>restore method. However, the screen is not going on, staying constant as i showed with photo below. I have opened the case of tablet, i have extracted the battery, and connected it again. No way, it does not continue, stays as constant like the photo. Is there anyone who can provide a solution?
Best
{
"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"
}

@agesilaus have tried flashing original Samsung firmware with Odin?

Hello All, much worse happened to me: after 8 years of resistance I figured 4.2 is way too old so went for the stock update on the device. It was downloading for too long, stopped 3 times during the process. I guess it is when it got damaged as the above nice samsung logo got stuck after reboot. When I tried to boot to recovery it does the flashing again (definition of insane - doing the same expect different result) and that's all hangs in the air again. (Exactly as it is shown above on the picture - waited until the tabled discharged.)
I could boot to download but the latest odin doesn't like the stock image (hoping it is that, if anyone has a safe copy a share would be appreciated).
One more info the machine is badly overheating, ADB connects, but says device is not authorised and I can't remember if I had any PC enabled for the device would be still alive...
Many thanks for any hints.

@xantbubus for that old firmware I'd take Odin 3.09.
Using the multiple file firmware is safer.
You don't say which device exactly.
Which region?

bmwdroid said:
@xantbubus for that old firmware I'd take Odin 3.09.
Using the multiple file firmware is safer.
You don't say which device exactly.
Which region?
Click to expand...
Click to collapse
Hello, thank you so much, apologies, it is sm-p602, the region is Turkey (althugh I live in Hungary but it was bought there).
Do you have a link for split firmware? They say even sm-p601 is working perfectly only the restriction on the call is lifted...

@xantbubus if sammobile, samfrew or others don't let you have them, use SamFirm_Reborn_0.3.6.3 which will definitely give you multiple files (if settings are correct ).

bmwdroid said:
@xantbubus if sammobile, samfrew or others don't let you have them, use SamFirm_Reborn_0.3.6.3 which will definitely give you multiple files (if settings are correct ).
Click to expand...
Click to collapse
Thanks, google was not really my friend on this. Btw, I resolved the issue. Unfortunately I needed to clean the data partition but after that it worked. I guess the 3.09 odin also played part as earlier it was trying to reflash instead of going to recovery so thank you all!

xantbubus said:
Thanks, google was not really my friend on this. Btw, I resolved the issue. Unfortunately I needed to clean the data partition but after that it worked. I guess the 3.09 odin also played part as earlier it was trying to reflash instead of going to recovery so thank you all!
Click to expand...
Click to collapse
Glad I could help.
Now you're entitled to hit "like"

bmwdroid said:
Glad I could help.
Now you're entitled to hit "like"
Click to expand...
Click to collapse
sorry, a bit new to this, hope this is enough

SM-N976V 5G Verizon

Since T-Mobile version SM-N976U came out today with Android 10 N976USQU1ASL3 would it make sense to try to flash the Verizon SM-N976V with it?

toshik1 said:
Since T-Mobile version SM-N976U came out today with Android 10 N976USQU1ASL3 would it make sense to try to flash the Verizon SM-N976V with it?
Click to expand...
Click to collapse
I have a N976V too, if that can work, please tell me :laugh:

toshik1 said:
Since T-Mobile version SM-N976U came out today with Android 10 N976USQU1ASL3 would it make sense to try to flash the Verizon SM-N976V with it?
Click to expand...
Click to collapse
same thing ive been trying to figure out.

I doubt it would work. They are not the same hardware. The T-Mobile has the x55 modem and the Verizon uses the x50 modem. They are different phones.

ourtech said:
The T-Mobile has the x55 modem and the Verizon uses the x50 modem.
Click to expand...
Click to collapse
And this is the only difference so far.

So if I try and flash my verizon n976v to tmobiles 976u, it won't work ? Has anyone successfully tried it and verified it works ?

It should work as long as you are within the same bin version - VZW for example on bin 2 recently. Everything should work modem is the only one at question. In theory driver for newer x55 modem should support x50, but who knows? The only gain right now is official Android 10, but VZW should get its own in a few weeks anyway.
I would also keep VZW ROM to flash it back.

No, this will not work.
Only U and U1 models are cross compatible, for flashing. You cannot flash U or U1 firmware to a model that ends in any other letter - and vice versa.

Good point! Thanks!

toshik1 said:
Since T-Mobile version SM-N976U came out today with Android 10 N976USQU1ASL3 would it make sense to try to flash the Verizon SM-N976V with it?
Click to expand...
Click to collapse
Anyone know why official firmware for Verizon Note 10+ 5G (SM-N976V) cannot be found on sammobile.com? I've yet to be able to locate it via their firmware database. They don't even list the SM-N976V model in my experience.

blbarrs said:
Anyone know why official firmware for Verizon Note 10+ 5G (SM-N976V) cannot be found on sammobile.com? I've yet to be able to locate it via their firmware database. They don't even list the SM-N976V model in my experience.
Click to expand...
Click to collapse
They don't have every single model. They don't have firmware for the G928V either, for example. And I'm sure I could find others, if I looked.
Thankfully, you can always grab the latest/newest version straight from SamFirm or Frija, any time that you want

If N976V/975U is written on the board, then it can be flashed with any firmware ? If not, why such a designation?
{
"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"
}

Alexx12 said:
If N976V/975U is written on the board, then it can be flashed with any firmware ? If not, why such a designation?
Click to expand...
Click to collapse
Doesn't matter what the board says. It matters which bootloader is flashed to it

iBowToAndroid said:
Doesn't matter what the board says. It matters which bootloader is flashed to it
Click to expand...
Click to collapse
According to imei the bootloader flashed for N975U. But it impossible to flash another bootloader for 976V ?

Alexx12 said:
According to imei the bootloader flashed for N975U. But it impossible to flash another bootloader for 976V ?
Click to expand...
Click to collapse
IMEI doesn't matter either. The only thing that matters is what model it shows as, in the Settings. But no matter which one it is, you can't flash another model's firmware to it

iBowToAndroid said:
IMEI doesn't matter either. The only thing that matters is what model it shows as, in the Settings. But no matter which one it is, you can't flash another model's firmware to it
Click to expand...
Click to collapse
OK. It shows N975U in the settings. Anyway , it seems strange that different models are written on the board. And also there is a 5G modem on the board.

Alexx12 said:
OK. It shows N975U in the settings. Anyway , it seems strange that different models are written on the board. And also there is a 5G modem on the board.
Click to expand...
Click to collapse
Well if you look up a teardown article or video, I'm sure that will be noted in there

iBowToAndroid said:
Well if you look up a teardown article or video, I'm sure that will be noted in there
Click to expand...
Click to collapse
Thanks. I'm afraid to even try to change an EEPROM. I'll leave it as it is , N975U

I know this is an older post however, I have a n976u I purchased carrier unlocked. I used https://t.me/Afaneh92UnlockChannell to unlock the bootloader and then went to town flashing everything I could find on to it. I have (or had) some photos showing different builds I had on that phone.
I am by no means putting down, discreditting or mean disrespect toward any developer, any builder, a manufacturer or website BUT some builds they say "wont work" and "not interchangeable" because of modems or chips or whatevers - however, my first 3 months I had n975u stock on my n976u. Took these pictures as an after thought so just service provider shows different from build, but you get the idea I hope.
I suppose bricking a $1k phone is not in most peoples to-do list and for sure I don't want that however, I am full aware the risk I take flashing my devices. I hope you are also aware of the risk. I flashed 100 different files from a patched odin to my Galaxy Note10+ 5g, and I dont care if the file was for SnapDragon or Exynos. Some files work for both and some dont. At 1 point I had 2 of every icon on the status bar... 2 battery icons, 2 time with seconds, 2 bandwidth icons and of course overlapping each other but the device still worked.
-- not a Samsung device but I have a Oneplus 7t Pro 5g McLaren TMobile device also and OrangeFox recovery is NOT for the Mclaren "they said" however, I flashed it and used it for a few months with no issues. I flashed a "do not flash-only boot" TWRP build as well for non-5g OnePlus 7t Pro device to my 5g McLaren and worked fine. Ive been using crDroid for a couple months now and bout to flash my Samsung with a newer build for n976u from https://t.me/userdata_aio_10_series

squirlnutz said:
I know this is an older post however, I have a n976u I purchased carrier unlocked. I used https://t.me/Afaneh92UnlockChannell to unlock the bootloader and then went to town flashing everything I could find on to it. I have (or had) some photos showing different builds I had on that phone.
I am by no means putting down, discreditting or mean disrespect toward any developer, any builder, a manufacturer or website BUT some builds they say "wont work" and "not interchangeable" because of modems or chips or whatevers - however, my first 3 months I had n975u stock on my n976u. Took these pictures as an after thought so just service provider shows different from build, but you get the idea I hope.
I suppose bricking a $1k phone is not in most peoples to-do list and for sure I don't want that however, I am full aware the risk I take flashing my devices. I hope you are also aware of the risk. I flashed 100 different files from a patched odin to my Galaxy Note10+ 5g, and I dont care if the file was for SnapDragon or Exynos. Some files work for both and some dont. At 1 point I had 2 of every icon on the status bar... 2 battery icons, 2 time with seconds, 2 bandwidth icons and of course overlapping each other but the device still worked.
-- not a Samsung device but I have a Oneplus 7t Pro 5g McLaren TMobile device also and OrangeFox recovery is NOT for the Mclaren "they said" however, I flashed it and used it for a few months with no issues. I flashed a "do not flash-only boot" TWRP build as well for non-5g OnePlus 7t Pro device to my 5g McLaren and worked fine. Ive been using crDroid for a couple months now and bout to flash my Samsung with a newer build for n976u from https://t.me/userdata_aio_10_series
Click to expand...
Click to collapse
I really don't understand the point of this post

Question A52S 5G (SM-A528B) Unlock bootloader camera failed

I unlocked the bootloader of my galaxy a52s 5g (SM-528B)
But the camera doesn't work on any application anymore it's a complete block and when I patch the boot.img with magisk I have a boot loop someone has the same problem or knows how to fix this?
{
"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"
}

Pinokaille said:
I unlocked the bootloader of my galaxy a52s 5g (SM-528B)
But the camera doesn't work on any application anymore it's a complete block and when I patch the boot.img with magisk I have a boot loop someone has the same problem or knows how to fix this?
View attachment 5413839
Click to expand...
Click to collapse
It seems it's a common behavior between newest samsung devices. Look at this video:

Good phone overall, but let down by manufacturer's restrictions. Like the Realme GT.

Did you get any message like "camera will not function" while in bootloader unlock menu?I bought this phone but if something like this is present then I will cancel,better to buy some other thing.

Arobase40 said:
There is NO problem with the camera when the Galaxy A52S 5G is unlocked !!!
Mine is working pretty fine so I guess the issue is somewhere else !
Click to expand...
Click to collapse
SM-A528B model ?​

Arobase40 said:
Yes !
Click to expand...
Click to collapse
Did you just unlock bootloader, or manage to root the phone as well?

i had the same issue after unlocking the BL, had to relock it again to get the camera to work.

deleted

Arobase40 said:
There is NO problem with the camera when the Galaxy A52S 5G is unlocked !!!
Mine is working pretty fine so I guess the issue is somewhere else !
Click to expand...
Click to collapse
Would you mind sending a screenshot as a verification that your bootloader is unlocked with working camera? Just split the screen with camera on the one half and developer options with OEM unlock option open on the other half

Pinokaille said:
I unlocked the bootloader of my galaxy a52s 5g (SM-528B)
But the camera doesn't work on any application anymore it's a complete block and when I patch the boot.img with magisk I have a boot loop someone has the same problem or knows how to fix this?
View attachment 5413839
Click to expand...
Click to collapse
This is PRECISELY what i see on my fold 3
if the camera returns AFTER BOOTLOADER RELOCK............
.................It is therefore confirmed that the A52 5G has the same booby trap as the Z fold 3
The Flip 3 does not have this however

I have the A52 5G (SM-A526B) and when I rooted my phone I had no problems with the camera. The only way to verify if OP's problem is intentional by Samsung or something went wrong in his unlocking process is if he (or someone else with the A52s 5G) posts a photo of the bootloader unlock screen. If it is intentional it will clearly say the camera will not function after unlocking

I have the same issue with my SM-A528B. I have unlocked the bootloader (The warning when unlocking the bootloader says nothing about the camera. It is just the regular warning about un-secure software etc.)
I used the latest Magisk to patch the boot image and flashed using Odin. Unfortunately it got stuck in a boot loop and I decided to flash the original boot image back. Now when starting the Samsung camera app, I get the "Camera Failed" error and the app closes. However, when testing other camera apps, some are able to use the front/selfie camera, but the rear camera always gives an error.
Update:
Flashing the BL, AP, CP and CSC did not help.
However locking the bootloader again made the camera work just fine. Thank you samsung for that little feature.

Arobase40 said:
Well no I can't do that as I re-locked my bootloader and that drive me to think there is something wrong with A52S...
Whenever my phone is unlocked (or supposed to be) or locked, the OEM option is always ON and recently I received an OTA update witch means my phone has never really been unlocked even when I got the message my system has been modified !!! ^^
That also explain why I couldn't root my phone with Magisk and the modified AP file.
BTW, if you have a rooted A52S 5G phone could you send me a build.prop file so I'll try to build a TWRP version for this model of phone, or if anyone else could send me this file ?
Click to expand...
Click to collapse
Thats sad to hear.
To get build.prop you can simply download the whole firmware from a site like samfw.com or with a tool like SamFirm and then extract it.

i can confirm that unlocking BL on SM-A528B makes camera unusable. black screen same as OP stated.

vladinc said:
i can confirm that unlocking BL on SM-A528B makes camera unusable. black screen same as OP stated.
Click to expand...
Click to collapse
Samsung fixed this camera issue on the Galaxy Z Fold 3, we hope it will do the same with the SM-A528B.
F

Arobase40 said:
SM-A528B bootloader is still not unlocked but there is a workaround when rooting it with Magiskv24.3.
You may have to repatch the AP file and flash it again, and then enable Zygist option in Magisk 24.3, install LSPosed-zygist module and SafetyNet Fix 2.2.1. reboot.
On, first try the camera won't work, so you have to force close the camera app in Settings, Applications.
Camera should work on next try.
You have to redo this same operation after every reboot... ^^
Click to expand...
Click to collapse
I did this step by step and everything was fine with root and camera working 100%.
Arobase40 said:
SM-A528B bootloader is still not unlocked but there is a workaround when rooting it with Magiskv24.3.
You may have to repatch the AP file and flash it again, and then enable Zygist option in Magisk 24.3, install LSPosed-zygist module and SafetyNet Fix 2.2.1. reboot.
On, first try the camera won't work, so you have to force close the camera app in Settings, Applications.
Camera should work on next try.
You have to redo this same operation after every reboot... ^^
Click to expand...
Click to collapse

Is there any fix for that? I unlocked the bootloader of my Galaxy A52s (SM-A528B/DS) and I get the damn error.
I just don't want to continue and root the phone unless I'm 100% sure that the camera will work...
Dammit Samsung!

Arobase40 said:
This is explained in post #22 just above !!! ^^
Click to expand...
Click to collapse
But that involves triggering knox. I want to avoid triggering knox (be it with root or flashing a patched AP) unless I'm 100% sure that camera will work.
Considering that just with the bootloader unlocked but nothing flashed the camera doesn't work.... I can't be 100% sure.
Thanks for trying to help, tho.

Arobase40 said:
You can't root this phone without triggering Knox !!!
Once again read post #22 to who I answered and read back the answer at post #23 about the result with the camera...
Click to expand...
Click to collapse
Once again: But that involves triggering knox. I want to avoid triggering knox
It's good that you spend your time trying to help people make the most out of their phones, but you try so hard to convince people on using your how-to's that you often ignore what compromises they are willing to make / not make.

Arobase40 said:
Listen, you asked to know how to root your phone with you camera working and I gave you the answer which is already an "exploit". If there was a way to avoid triggering Knox you can imagine I would use myself it asap as any other users too but there is none !!!
Want to root your phone ? Then you have to make this compromise, if not, then don"t root your phone Period
Click to expand...
Click to collapse
Read again, but this time read right please:
A52S 5G (SM-A528B) Unlock bootloader camera failed
I unlocked the bootloader of my galaxy a52s 5g (SM-528B) But the camera doesn't work on any application anymore it's a complete block and when I patch the boot.img with magisk I have a boot loop someone has the same problem or knows how to fix this?
forum.xda-developers.com
Nowhere in this thread I asked how to root my phone....
Get out and do something else besides trying to get everyone to follow your xda tutorials. Most importantly read correctly before going off on someone for not following your suggestions.
You might think that I'm nobody to tell you something like that, but trust me... I'm doing you a favour, it will help you to not be perceived as a maniac easy to trigger whenever someone rejects his suggestions.

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)?