Develop Bugs

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

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

[BOOT] Remove Boot Warning - Tested on Exynos - After Root - 21st October 2019

Hello everyone ...
I hope you all are fine...
For those who are looking for a way to remove the warning for device other than Note 10 versions, please go to the link:
[BOOT] Remove Boot Warning - All Exynos Devices - After Root - Tutorial
Click to expand...
Click to collapse
So after following the Rooting guide (Bless @dr.ketan , @geiti94 & @ianmacd)
I followed mainly this thread for the ROOT:
[Guide] How to root Note10/Note 10+ & Flash TWRP (Exynos only)
Sub-threads that are useful:
[RECOVERY][UNOFFICIAL] TWRP for Galaxy Note 10 (Exynos)
[Pie] [System-as-root] Multidisabler: encryption, Vaultkeeper, proca, auto-restore
After getting the root,
The boot-up screen wasn't like we were used to,
There are many warnings which kind of screams ROOTED device aside from not being beautiful...
I have decided to grab the images and replace them with the original logo of my Samsung Galaxy Note 10 plus & Non Plus...
Instructions are very simple and easy to follow:
Exynos is working, (Snapdragon owners: This does not work for you, please wait until I figure it out)
Download the file "XXXXX_YYYYY_FIX_BL.tar" in the attachments...
YYYYY = choose your device 10 or 10 PLUS because dimensions are different, normal or 5G because of different logos...
XXXXX = STOCK or CENTER, look at the attached Gifs to understand the difference...
Switch off your phone and then go into the download mode (vol up + vol down and connect USB)...
Start Odin (if you don't have Odin, grab it from this thread)...
Place the file "XXXXX_YYYYY_FIX_BL.tar" in the BL section...
OPTIONAL: make sure auto-reboot is off in Odin (personally I prefer to reboot the phone myself)...
Once the flashing is complete, disconnect and exit the download mode...
Enjoy looking at your phone
I attached different gifs in the second post #2 showing before BL flashing and after the flashing, tested on Exynos SM-N970, SM-N971, SM-N975 & SM-N976...
Again, make sure you flash the right fix, "XXXXX_YYYYY_FIX_BL.tar"
YYYYY = choose your device 10 or 10 PLUS because dimensions are different, normal or 5G because of different logos...
XXXXX = STOCK or CENTER, look at the attached Gifs to understand the difference...
Again, I thank @dr.ketan , @geiti94 & @ianmacd for their time to make root possible...
Don't Forget to Smash the THANKS Button
and
if you're very happy, support or buy me a cup of coffee through a donation, that would be nice ​
Happy Modification ...

Changelog:
(14/12/2020) XDA removed the gifs because of the attachment limit per post, added attachments here...
(21/10/2019) Samsung Snapdragon confirmed, exynos doesn't work with snapdragon, I need snapdragon volunteers to remove the triangle...
(22/09/2019) Samsung Galaxy Note 10+ 5G - SM-N976...
(22/09/2019) Samsung Galaxy Note 10 5G - SM-N971...
(20/09/2019) Samsung Galaxy Note 10+ - SM-N975...
(20/09/2019) Samsung Galaxy Note 10 - SM-N970...
Attached Gifs:
Note 10 Before & After | Note 10 5G Before & After | Note 10+ Before & After | Note 10+ 5G Before & After
{
"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"
}
| | |

Snapdragon owners, it has been confirmed, all exynos models won't work for you, thus I have to make snapdragon version, if you have the patience and time, please volunteer to solve this, all volunteers will be credited in the thread, thank you in advance...
Exynos owners, If you have a different boot-up logo other than the what I have shared,
share your Firmware BL mentioning your device model...
(it's 3 MB file, I won't download 5.3GB ROM that would be useless for me, You can download it since it will benefit your phone if you need to flash stock and so, it's a win-win situation )
This is a zero-risk method and no need to backup as your device will boot-up normally
as you're flashing images, not software or any part of the system
(BUT DO BACKUP, YOU NEVER KNOW WHAT MIGHT GO WRONG)

Dante63 said:
If you have a different boot-up logo other than the Exynos one,
share your Firmware BL mentioning your device model...
This is a zero-risk method and no need to backup as your device will boot-up normally
as you're flashing images, not software or any part of the system (BUT DO BACKUP, YOU NEVER KNOW WHAT MIGHT GO WRONG)
Click to expand...
Click to collapse
https://www.sammobile.com/samsung/g...e/SM-N976B/BTU/download/N976BXXU1ASHE/289265/
i use note 10 + 5G N976B MODEL

minidude2012 said:
https://www.sammobile.com/samsung/g...e/SM-N976B/BTU/download/N976BXXU1ASHE/289265/
i use note 10 + 5G N976B MODEL
Click to expand...
Click to collapse
Share the BL of your firmware, it's 3 MB file, spare me the 5.3 GB download please :crying:...
Besides, you will be using the stock ROM since it's compatiable with your phone, not mine , a win-win situation...
And once I get the BL of your N976B, it will be done before you know it (unless I am sleeping :angel...

Galaxy Note+ SM-N975F/DS
Thank you!
~~
Oops. Just realized you've covered this one. Sorry about that!

Dante63 said:
Share the BL of your firmware, it's 3 MB file, spare me the 5.3 GB download please :crying:...
Besides, you will be using the stock ROM since it's compatiable with your phone, not mine , a win-win situation...
And once I get the BL of your N976B, it will be done before you know it (unless I am sleeping :angel...
Click to expand...
Click to collapse
Sorry I'll get it downloaded in about a week no WiFi currently

Pinan said:
Galaxy Note+ SM-N975F/DS
Thank you!
~~
Oops. Just realized you've covered this one. Sorry about that!
Click to expand...
Click to collapse
No problem, Indeed I did cover that, I believe I am missing the 5G for 10 & 10+ and custom companies logos ...
minidude2012 said:
Sorry I'll get it downloaded in about a week no WiFi currently
Click to expand...
Click to collapse
No worries, bear with the annoying warning till you get it whether you download it or someone else posts it...

Dante63 said:
No problem, Indeed I did cover that, I believe I am missing the 5G for 10 & 10+ and custom companies logos ...
No worries, bear with the annoying warning till you get it whether you download it or someone else posts it...
Click to expand...
Click to collapse
Tbh I haven't rooted yet waiting for device tree off another Dev to work on custom ROM before rooting

Dante63 said:
Enjoy looking at your phone
Click to expand...
Click to collapse
Thank you very much! Done. And it works great.:good:

get rid of the powered by android and knox while you're at it

zzcool said:
get rid of the powered by android and knox while you're at it
Click to expand...
Click to collapse
Hmmm, after removing "powered by android", the remainder won't be center anymore...
Is it really a good idea to remove the "powered by android"and have Samsung name upper offset...

Dante63 said:
Hmmm, after removing "powered by android", the remainder won't be center anymore...
Is it really a good idea to remove the "powered by android"and have Samsung name upper offset...
Click to expand...
Click to collapse
move the samsung logo down so it's perfectly centered or get rid of all and just make it a black screen the amount of time this shows would be so small you wouldn't notice

zzcool said:
move the samsung logo down so it's perfectly centered or get rid of all and just make it a black screen the amount of time this shows would be so small you wouldn't notice
Click to expand...
Click to collapse
Well I'll try to center it as for black, it won't be small, after rooting, there will be approximately 5 to 8 seconds time margin...
As the phone tends to show you the bootloader warning and wants you to hit the power button to continue (have a second look at the gif I attached, you'll see the order of boot is unlike what we used to have as in older rooted phones) so when you try to boot, you'll be wondering if it booted up or not, hit recovery or not...
So I'll try to have it centered...

Dante63 said:
Well I'll try to center it as for black, it won't be small, after rooting, there will be approximately 5 to 8 seconds time margin...
As the phone tends to show you the bootloader warning and wants you to hit the power button to continue (have a second look at the gif I attached, you'll see the order of boot is unlike what we used to have as in older rooted phones) so when you try to boot, you'll be wondering if it booted up or not, hit recovery or not...
So I'll try to have it centered...
Click to expand...
Click to collapse
so theres no way around an 8 second boot? makes me reconsider ever flashing it then, as for the logo try adding a loading text or anything i always hate logos of any kind.

Dante63 said:
No problem, Indeed I did cover that, I believe I am missing the 5G for 10 & 10+ and custom companies logos ...
No worries, bear with the annoying warning till you get it whether you download it or someone else posts it...
Click to expand...
Click to collapse
Would you mind doing oone for us tab s5e owners? Heres the file....
https://drive.google.com/file/d/1bzj2dS6eVZne8fvLG577J50U81NhNVPi/view?usp=sharing

suzook said:
Would you mind doing oone for us tab s5e owners? Heres the file....
https://drive.google.com/file/d/1bzj2dS6eVZne8fvLG577J50U81NhNVPi/view?usp=sharing
Click to expand...
Click to collapse
The device model is much better for me to know what device since I can google it,
did you say "US Tab S5E"...?
From my understanding, you are requesting for a different device, other than Note 10...
If so, give me some time, I'll create a DIY thread for that just like my SoundMod DIY...
Bare with the warning, as soon as I'm done, I'll either @ you or I'll reply to you...
zzcool said:
so theres no way around an 8 second boot? makes me reconsider ever flashing it then, as for the logo try adding a loading text or anything i always hate logos of any kind.
Click to expand...
Click to collapse
Maybe in the future someone can enhance that part, my role here is removing the ugly warning, you will understand if you have root as it seems you still didn't obtain it ...

Dante63 said:
The device model is much better for me to know what device since I can google it,
did you say "US Tab S5E"...?
From my understanding, you are requesting for a different device, other than Note 10...
If so, give me some time, I'll create a DIY thread for that just like my SoundMod DIY...
Bare with the warning, as soon as I'm done, I'll either @ you or I'll reply to you...
Maybe in the future someone can enhance that part, my role here is removing the ugly warning, you will understand if you have root as it seems you still didn't obtain it ...
Click to expand...
Click to collapse
Yes, its SM-T720. Take your time, and yes, you could pm me. I would be willing to try it myself with instructions. Thanks

Dante63 said:
The device model is much better for me to know what device since I can google it,
did you say "US Tab S5E"...?
From my understanding, you are requesting for a different device, other than Note 10...
If so, give me some time, I'll create a DIY thread for that just like my SoundMod DIY...
Bare with the warning, as soon as I'm done, I'll either @ you or I'll reply to you...
Maybe in the future someone can enhance that part, my role here is removing the ugly warning, you will understand if you have root as it seems you still didn't obtain it ...
Click to expand...
Click to collapse
my mate 10 pro is rooted i thought the long boottime was specific to huawei not all phones

Anychance there is a 10+ 5G Boot screen available?

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 Worth rooting?

Is is worth rooting the Pixel 6 Pro now that one doesn't have to disable verity and because repainter now requires root to apply the AMOLED background? If so, what are the steps for installing OTAs, and what are the chances of bricking your device. If you have rooted, do you use quick switch and do you think it is worth it? ThanksIs is worth rooting the Pixel 6 Pro now that one doesn't have to disable verity and because repainter now requires root to apply the AMOLED backround? If so,

It has always been worth it imho. Adaway, V4A, SwiftBackup, AinurNarsil, Substratum... there is a lot of stuff you can't do without root. Especially decent adblock, backup and better music is important to me. All stuff Google could implement on its own without issues, but Google being Google...
With Zygisk/hide & the fix for SafetyNet, all my apps/banking stuff/GPay is working fine, so there is no "downside" to rootinng, except updating firmware.

By updating firmware you mean OTAs right? What are the steps for installing them?

Divine Bicycle said:
By updating firmware you mean OTAs right? What are the steps for installing them?
Click to expand...
Click to collapse
Hi. Click the How To Guide filter above the Pixel 6 Pro section and you'll find all the directions you need.
Keep in mind that although disabling Verity and Verification are no longer required for root, some custom kernels for stock still require that. If you're not going to ever use a custom kernel, then it's not a concern.
At least one custom kernel developer wasn't sure if it was still necessary so still advises it for use with their custom kernel.
At this point, I'm reversing my own personal expression and still planning on disabling then when the late January update comes out side I use that custom kernel, at least until another guinea pig reports it's not necessary, or I have time to make sure I have everything backed up and try it myself.
It's possible I'll have time when that update comes out.

Morgrain said:
It has always been worth it imho. Adaway, V4A, SwiftBackup, AinurNarsil, Substratum... there is a lot of stuff you can't do without root. Especially decent adblock, backup and better music is important to me.
Click to expand...
Click to collapse
Can you explain the "better music" part; and, is substratum still in development? I thought it was heavily discontinued.

RetroTech07 said:
Can you explain the "better music" part; and, is substratum still in development? I thought it was heavily discontinued.
Click to expand...
Click to collapse
V4A is supposed to make your music sound better. I've never used it, but a lot of rooters swear by it.

roirraW edor ehT said:
At this point, I'm reversing my own personal expression and still planning on disabling then when the late January update comes out side I use that custom kernel, at least until another guinea pig reports it's not necessary, or I have time to make sure I have everything backed up and try it myself.
It's possible I'll have time when that update comes out.
Click to expand...
Click to collapse
I am doing the same. I have it disabled on the December build and will keep it disabled on the January build just so I have some flexibility if I decided to use a kernel that requires it to be disabled. Currently I'm on Kiri so I don't need it disabled, but my fickle mind may want to switch for whatever mad reason it gives me

Lughnasadh said:
I am doing the same. I have it disabled on the December build and will keep it disabled on the January build just so I have some flexibility if I decided to use a kernel that requires it to be disabled. Currently I'm on Kiri so I don't need it disabled, but my fickle mind may want to switch for whatever mad reason it gives me
Click to expand...
Click to collapse
I'm not entirely sure on this...have we established whether disabling verity/verification still results in Rescue Party on the factory boot image, patched or no?

roirraW edor ehT said:
V4A is supposed to make your music sound better. I've never used it, but a lot of rooters swear by it.
Click to expand...
Click to collapse
I use it alongside JamesDSP (I really prefer the bass of JamesDSP over V4A) and have since Ice Cream Sandwich. I'm not sure if "better" is the right word, but it does allow you to adjust the sound more the way you want it.

Lughnasadh said:
I am doing the same. I have it disabled on the December build and will keep it disabled on the January build just so I have some flexibility if I decided to use a kernel that requires it to be disabled. Currently I'm on Kiri so I don't need it disabled, but my fickle mind may want to switch for whatever mad reason it gives me
Click to expand...
Click to collapse
I love how often you find the upside-down smiley useful. LOL! I often don't know whether to like, love, laugh, or wow at your posts. Madness for everyone!
Edit: Even my one cat thinks it's funny.
{
"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

Sorry guys i have to post here since no one answered my 5 years ago posts asking about stuff, so i have to say it here
Note 10 plus when are we getting the ui 4.0?? It s 11th of jan already and i have only december security update

ramharb said:
Sorry guys i have to post here since no one answered my 5 years ago posts asking about stuff, so i have to say it here
Note 10 plus when are we getting the ui 4.0?? It s 11th of jan already and i have only december security update
Click to expand...
Click to collapse
Hi, check over here:
Samsung Galaxy Note 10+
The Samsung Galaxy Note 10+ is a 6.8" phone with a 1440x3040p resolution display. The Exynos 9825/Snapdragon 855 chipset is paired with 12GB of RAM and 256/512GB of storage. The main camera is 12+12+16MP and the selfie camera is 10MP. The battery has a 4300mAh capacity.
forum.xda-developers.com
Cheers

ramharb said:
Sorry guys i have to post here since no one answered my 5 years ago posts asking about stuff, so i have to say it here
Note 10 plus when are we getting the ui 4.0?? It s 11th of jan already and i have only december security update
Click to expand...
Click to collapse
This really isn't the place to ask about anything not related to the Pixel 6 Pro. As for as the P6P and the January update, it's been previously announced that it would come for the P6 & P6P in late January.
December 2021 Update Paused

V0latyle said:
I'm not entirely sure on this...have we established whether disabling verity/verification still results in Rescue Party on the factory boot image, patched or no?
Click to expand...
Click to collapse
I haven't seen or heard of any changes that would say otherwise, but I could be wrong. The only change that I'm aware of is the change in Canary Magisk 23016 that eliminates the need to disable verity & verification when rooting. Thus, I would imagine that disabling those would still result in Rescue Party on the stock boot image since Canary Magisk is not involved, as well as on some custom kernels without being rooted (e.g. CleanSlate where tbalden isn't sure if it is still needed with his kernel and I believe he disables verity & verification just in case).
So my understanding is that on stock boot image disabling those will result in Rescue Party, on a Canary Magisk 23016 patched boot image it will not, and for some custom kernels (without being rooted) it may or may not depending on the kernel and whether the magiskboot binaries the kernel uses were updated to 23016.
That is, if I'm understanding you correctly.

roirraW edor ehT said:
I love how often you find the upside-down smiley useful. LOL! I often don't know whether to like, love, laugh, or wow at your posts. Madness for everyone!
Edit: Even my one cat thinks it's funny.
Click to expand...
Click to collapse
Embrace the madness!!!

Lughnasadh said:
I haven't seen or heard of any changes that would say otherwise, but I could be wrong. The only change that I'm aware of is the change in Canary Magisk 23016 that eliminates the need to disable verity & verification when rooting. Thus, I would imagine that disabling those would still result in Rescue Party on the stock boot image since Canary Magisk is not involved, as well as on some custom kernels without being rooted (e.g. CleanSlate where tbalden isn't sure if it is still needed with his kernel and I believe he disables verity & verification just in case).
So my understanding is that on stock boot image disabling those will result in Rescue Party, on a Canary Magisk 23016 patched boot image it will not, and for some custom kernels (without being rooted) it may or may not depending on the kernel and whether the magiskboot binaries the kernel uses were updated to 23016.
That is, if I'm understanding you correctly.
Click to expand...
Click to collapse
For what it's worth, back awhile after I had been rooted with Magisk Canary 23015, I temporarily restored the stock unrooted boot.img and was able to boot fine after verity and verification had already been disabled. But possibly you're talking of a slightly different scenario.

roirraW edor ehT said:
For what it's worth, back awhile after I had been rooted with Magisk Canary 23015, I temporarily restored the stock unrooted boot.img and was able to boot fine after verity and verification had already been disabled. But possibly you're talking of a slightly different scenario.
Click to expand...
Click to collapse
Yeah, that makes sense because you only restored the stock boot image, but not the stock vbmeta so verity and verification remained disabled, allowing you to flash whatever you heart desires.

I'll test it right now. Stock P5, January update, Magisk patched boot image. Let's see what happens...
Reflashed vbmeta and disabled verity/verification. Boot image is patched. Result: Rescue Party.
Reflashed unpatched boot image. Result: Rescue Party
Reflashed vbmeta without options, reflashed patched boot image. Result: Successful boot.

Alright, I was thinking about not rooting at first but now I'm getting that itch. Welp.....time to try and root this joint

roirraW edor ehT said:
At this point, I'm reversing my own personal expression and still planning on disabling then when the late January update comes out side I use that custom kernel, at least until another guinea pig reports it's not necessary, or I have time to make sure I have everything backed up and try it myself.
Click to expand...
Click to collapse
I've been usng Dec build without veritfy/verification disabled (with Canary 23016 & Kiri 1.40) since mid December & have no issues to report. Guinea pig status: achieved?