Database Develop

I believe I have bricked my HTC One Mini 2?

Was at work using both my company phone (iPhone 5) and my personal phone (HTC One Mini 2) just fine. Put my personal phone away to get on with actual work and came home at around 5:30'ish. Played a bit ("a bit") until about 9/10pm (I think?) whereby I looked for my phone to just check things like WhatsApp and Snapchat and the phone wasn't turning on when I was holding the power button. I just thought to myself "huh, the battery must be dead" and put it to charge and the charging LED (as well as the charging screen with the "do not distribute outside htc blabla" dev screen) displayed so I just assume it's charging as per usual. Fast forward to about 1am, I have finished using my computer and decide to hop into bed. I go to turn on my phone by first powering down with power, vol up and vol down (as usual) and then try to boot the phone up. It boots as normal up until the O/S loading screen with a pac-man boot animation (I have PAC ROM installed) whereby it will freeze on the "game over" image of the boot animation and then proceed to go to a black screen. I thought to myself "hm, must be a mistake or something" and try it again to no avail. So I then go into recovery to do a fresh install and I try to wipe the phone and I do a factory reset in twrp, but upon trying to format data, the progress bar doesn't move (and so I left it overnight as I couldn't be bothered to wait). Upon leaving it overnight (1am to 7am) to format the data, I wake up to see that the progress bar hadn't moved at all from 0%. I then just thought "maybe the phone has actually formatted it but hasn't updated the image on screen so me being the dumbo I am, decided to force shut down the phone (with power, volup and voldown) and upon trying to boot the phone up again, it displays the HTC logo with the red writing, tries to boot into the O/S, fails, and then tries to boot into recovery and gets stuck in a boot loop (it will show the twrp logo and then a black screen, twrp logo and then black screen etc.). I have tried to flash twrp again (without first removing the twrp currently on it) but I was wondering what I could do in this situation. I am able to access the bootmenu (for hboot and fastboot) but nothing else.
TL;DR: I think I bricked my HTC One Mini 2. Came home, charged phone and phone got stuck at boot animation. Wiped phone in recovery, it got stuck on formatting data and now It can't boot into the O/S since it's wiped and it can't boot into Recovery for whatever reason.

DistincTHD said:
blah blah
Click to expand...
Click to collapse
This is not Facebook, go straight to the point.
Did you install a different kernel?

kativiti said:
This is not Facebook, go straight to the point.
Did you install a different kernel?
Click to expand...
Click to collapse
{
"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"
}
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.

DistincTHD said:
[IMG="HTC Dev Message"]
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Oops, Just realised you meant the whole post, not just the blah blah bit within the post. But yeah what I did, I explained above and in the original post. I basically just told a story to give a better idea of what generally happened before the phone just pooped out on me.

DistincTHD said:
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.

kativiti said:
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.
Click to expand...
Click to collapse
I can't access twrp recovery but I do have fastboot enabled and working and I can access the boot menu so how would I go about wiping everything before re-flashing the recovery and then re-installing the o/s and everything else?

Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment

DistincTHD said:
Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment
Click to expand...
Click to collapse
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...

kativiti said:
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...
Click to expand...
Click to collapse
Right, so before I read that message, I flashed stock recovery and tried to reformat data and now It won't let be get into the boot menu and the HTC dev writing is gone (so I think it's locked again). On top of this, it just keeps booting into the reformatting data screen and just ends up hanging so I think I will let the battery drain or something (no idea how long it would take, probably days) and then try again from there. Pretty sure it is bricked now though lol welp. Is there any way to cancel a format?

Root SM-t580

I try to root a Galaxy Tab 6A (SM-T580).
-I tried some CF-Autoroot images, but their is no image for the SM-T580.
-I tried also to install TWRP with no success. The device do not boot in Recovery Mode with the TWRP image.
The device runs on Marshmallow 6.0.1.
Can somebody help me please?

I too would love and greatly appreciate any help! It's a great tab for the money

hell2003 said:
I try to root a Galaxy Tab 6A (SM-T580).
-I tried some CF-Autoroot images, but their is no image for the SM-T580.
-I tried also to install TWRP with no success. The device do not boot in Recovery Mode with the TWRP image.
The device runs on Marshmallow 6.0.1.
Can somebody help me please?
Click to expand...
Click to collapse
You flashed custom recovery ? the bootloader is not locked?

I tried a twrp custom recovery image. But I cant start the recovery mode. I do not know the status of the bootloader. How can i check that?

http://forum.xda-developers.com/android/development/recovery-official-twrp-gtaxlwifi-galaxy-t3437666
@jcadduono did it !
Let's try

bws78 said:
http://forum.xda-developers.com/android/development/recovery-official-twrp-gtaxlwifi-galaxy-t3437666
@jcadduono did it !
Let's try
Click to expand...
Click to collapse
what do you guys think of my new shirt isn't it awesome
{
"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"
}

bws78 said:
http://forum.xda-developers.com/android/development/recovery-official-twrp-gtaxlwifi-galaxy-t3437666
@jcadduono did it !
Let's try
Click to expand...
Click to collapse
Thank you very much, this works for me.

hell2003 said:
Thank you very much, this works for me.
Click to expand...
Click to collapse
don't thank me, thank @jcadduono in the official thread

Data partition encryption prevents root without a .zip rom
hell2003 said:
I try to root a Galaxy Tab 6A (SM-T580).
-I tried some CF-Autoroot images, but their is no image for the SM-T580.
-I tried also to install TWRP with no success. The device do not boot in Recovery Mode with the TWRP image.
The device runs on Marshmallow 6.0.1.
Can somebody help me please?
Click to expand...
Click to collapse
You can disable frp lock by removing your Google account. This will allow you to flash twrp with Odin.
Disable auto reboot in Odin before flashing twrp. After flashing twrp you can reboot into recovery by holding power and volume down to turn the device off. Then once it's off hold volume up home and power to reboot into twrp.
Now the only problem is you can't flash supersu.zip without formatting data first from the twrp wipe data main screen. This is because the data partition is unavailable due to encryption. Formatting data partition removes encryption and allows you to flash supersu, but now device won't boot after formatting data unless you flash a ROM from within twrp. Only problem is that there are no such Roms yet.
If anyone could create a stock or custom ROM that is a flashable zip you'd be the MAN!
Until then I don't think we'll be able to root our device.

Still no roms available?

Now the only problem is you can't flash supersu.zip without formatting data first from the twrp wipe data main screen. This is because the data partition is unavailable due to encryption. Formatting data partition removes encryption and allows you to flash supersu, but now device won't boot after formatting data unless you flash a ROM from within twrp. Only problem is that there are no such Roms yet.
Click to expand...
Click to collapse
Does this mean that if you just root the device that the data partition is encrypted and cant use it as if it was not rooted?
Tried this last night but got the Fap lock. Didnt know about the google bit.
I want to download my current rom and backup is this possible?
I havent done this stuff since the HTC HD2 days
Thanks.
Rob.

I've successfully bypassed the Google FRP Lock on SM-T580 and posted the instructions in [URL="https://forum.xda-developers.com/galaxy-tab/help/bypass-frp-sm-t580-2016-t3446958]this forum[/URL]. If you cant figure it out send me a message and I'll walk you through it

hi
only for root..
Can i use cf-autoroot?

abarth83 said:
hi
only for root..
Can i use cf-autoroot?
Click to expand...
Click to collapse
Hanyone tried it?

Instructions
kleptobismol said:
I've successfully bypassed the Google FRP Lock on SM-T580 and posted the instructions in [URL="https://forum.xda-developers.com/galaxy-tab/help/bypass-frp-sm-t580-2016-t3446958]this forum[/URL]. If you cant figure it out send me a message and I'll walk you through it
Click to expand...
Click to collapse
Hello, Can you repost instructions can't get page to load
This site can’t be reached
%22https’s server DNS address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN
Thanks

ohiostater86 said:
Hello, Can you repost instructions can't get page to load
This site can’t be reached
%22https’s server DNS address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN
Thanks
Click to expand...
Click to collapse
I was having the same problem, but i figured it out last night. Without OTG cable, Odin, SideSync, Realtek, or a PC. I'd been messing with it for 3 days, so Im not 100% sure of what everything said and i'm definitely not going to relock it to try an duplicate it, but if you've been all over youtube then you've seen methods that require a wifi connection, (I found it easiest to use my phone's wifi hotspot) you disconnect your hotspot or unplug your router immediately when it says checking for software update, which appears after clicking accept on the privacy policy. (Again it's easier to just turn off the hotspot than to unplug your router" When done correctly it souls say "couldn't sign in" and then the next screen will either ask you to set up time and date or it asks you to add a name to the tablet (can't remember which is first) then asks to set up a screen lock passcode or pattern (set up either one), after doing all this 100 times I noticed it asked me if i wanted to set up a IMAP/POP3 account to use within the Gmail app (which I'd been skipping) but for some reason it didn't give me this option every time. You have to be connected to the internet for the next part so if you haven't already go ahead and turn your hotspot back on or router and add any email address other than a Gmail (I used my yahoo account) then follow through with the setup into it takes you back to the very first screen you see when you turned on the tablet. Now just turn the tablet screen off and back on (just the screen, do not power down the tablet) put in your lockscreen password and now In the top right corner there should be a little yellow icon which lets you switch users (if you see this, you've got it beat) now create a new user signing into your Gmail and Samsung accounts (if you don't have one, create a new account) once you're done with that it will take you to the home screen, pull down the notification bar and go into settings (notice since you're on an added user you can't factory reset the device) find "Users", and then switch back to the owner profile, it then tells you that you still need to set up the tablet to continue. Once i clicked okay it now let me pull down the notification bar to access settings, but this time you're on the owners account so you can factory reset it, go to "Back up and Reset" and then go ahead and factory reset it again. If done correctly the FRP will no longer be on the tablet.

I rooted my T580 with this german howto:
https://www.android-hilfe.de/forum/...sm-t585-samsung-galaxy-tab-a-2016.788225.html
Root is ok now! But unlocking the LockScreen needs 5-10 seconds now. Has this sth to do with Knox 0x1 ?

Getting "Your device is corrupt" message and I want to start completely fresh.

Getting "Your device is corrupt" message and I want to start completely fresh.
I had setup a Nexus 6 a couple years back for someone who was mostly blind and I used tasker to let them do most things they needed by voice only.
It was working fine until a couple days ago when somehow the device upgraded from Lollipop to Android 7.0. The way I initially unlocked the phone and obtained root, I didn't think it would ever be able to upgrade unless I intervened but it finally happened seemingly on its own.
Anyway, it lost root and many of the tasker commands stopped working because of it so I tried to get it back by:
1) Using fastboot to flashe twrp-3.1.1-0-shamu.img to recovery
2) Booting into recovery and installing SuperSU with TWRP after I made a backup
After that, the phone booted back up normally but still didn't have root access so I restarted again but when I tried to get into recovery I got a "no command" message. I was finally able to get passed that by pressing volume down (I think) and it gave me the standard android factory reset, wipe cache, etc. options. I tried wiping the cache and then after reboot I got this message:
{
"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"
}
And then it just disappears after a few seconds and the phone will not boot up.
Now though I can still get back into the bootloader menu with Power and Volume Down and even get back to the TWRP recovery where I tried restoring the backup I made before installing SuperSU but the same problem occurs.
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?

LaTropa64 said:
I had setup a Nexus 6 a couple years back for someone who was mostly blind and I used tasker to let them do most things they needed by voice only.
It was working fine until a couple days ago when somehow the device upgraded from Lollipop to Android 7.0. The way I initially unlocked the phone and obtained root, I didn't think it would ever be able to upgrade unless I intervened but it finally happened seemingly on its own.
Anyway, it lost root and many of the tasker commands stopped working because of it so I tried to get it back by:
1) Using fastboot to flashe twrp-3.1.1-0-shamu.img to recovery
2) Booting into recovery and installing SuperSU with TWRP after I made a backup
After that, the phone booted back up normally but still didn't have root access so I restarted again but when I tried to get into recovery I got a "no command" message. I was finally able to get passed that by pressing volume down (I think) and it gave me the standard android factory reset, wipe cache, etc. options. I tried wiping the cache and then after reboot I got this message:
And then it just disappears after a few seconds and the phone will not boot up.
Now though I can still get back into the bootloader menu with Power and Volume Down and even get back to the TWRP recovery where I tried restoring the backup I made before installing SuperSU but the same problem occurs.
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?
Click to expand...
Click to collapse
I'm not sure what to tell you, there's a lot of complication between these things but mostly seems like it'd include Re-flashing stock os 7.0 and obtaining root thru Android 7 without flashing any rom
Sent from my Z988 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 08:08 AM ----------
And by complication I mean the whole concept of just starting over fresh
Sent from my Z988 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 08:09 AM ----------
Good luck tho
Sent from my Z988 using Tapatalk

LaTropa64 said:
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?
Click to expand...
Click to collapse
Download a factory image from Google developer site. That site gives instructions to set-up your PC for fastboot (if you need it) and there is a flash all script in the download to handle the flash through fastboot. This thread will give you an overview. Using the flash all script will wipe the entire phone!
You can also fastboot flash each partition manually. If you use the -w flag, it will wipe all user data from the phone.
Be warned, the probability is you'll wipe the internal (user data) and if you want to try to back up first, you should be able to boot into TWRP and use ADB to do an a back up of user data to your PC using:
adb pull /path/to/files /home/[your username]/
E.G.
Windows:
adb pull /sdcard C:\Users\[your username]\Desktop
Linux:
adb pull /sdcard /home/[your username]/
You'll need administrator privileges on the PC to specify the output path.
---Edit---
You might look into the tasker beta to work with the newer nougat releases. I will say, all of my tasker profiles continued to work regardless of OS version with the exception of those relying on secure settings. Those I updated to use auto tools. There are other work around as well.

Follow what @ktmom says to get the device all straightened out firmware wise. As the device totally skipped Android 6 in doing its upgrade there could be undesired leftovers from the original install. Once you've installed the latest stock firmware from Google you can start over with your customizations, but be aware that installing TWRP, rooting the device, or both will cause the "device is corrupt" message you're seeing. That message will remain on every boot until a custom kernel which ignores dm-verity is installed.

In a few months, Galaxy S8 will get Bixby Voice so you could get one of them.
Sent from my Z988 using Tapatalk

Who in the hell would want to use Bixby?

Just updated from v14 to v15 and now phone is stuck in fastboot

I admit, I am a little out of my depth on this so would appreciate any help on how to fix this as fast as possible, I would rather not restore a TWRP backup as it is not the most recent.
I updated via direct, it completed, I selected reboot and now phone is stuck in fastboot. I have tried "fastboot continue", "fastboot reboot" and of course tried via TWRP, it always boots back into fastboot. (See update below)
I am googling it and not finding much.
Any ideas?
{
"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"
}
So far it seems v15 simply will not work on my phone.
Update:
Reinstalling v15 via TWRP - Same result, stuck at fastboot
Ran uninstaller, cleared dalvik and cache, rebooted - Phone stuck in boot, rebooted and it booted successfully
Installed Magisk 14 via TWRP, booted normally.

Same problem here.
Running samstock rom on 925w8.
Stock Kernel and Modem

I have the same problem.
I flashed with twrp v14 again, but after that it flashes all th time in my galaxy begin screen.
tried to use uninstall magisk and installed v14 and v15 again.
but stil the same
tried to recover in twrp with backup but stil the same.
Can somebody help
'What can i do so i can restart my phone.
How do i get back to factory settings?

Same here with Umidigi Z
No boot on 14.6 and 15
If you uninstall magisk and the phone don't boot you have to restore boot in twrp
If you have no backup then make a full backup, wipe the phone (maybe) / flash it again make a backup of the boot partition and then restore system and data from the TWRP full backup before

Yeah I have the very same problem on my galaxy S8 plus (exynos).. This will be the last time for me to update an app like that without making a backup......

My Phone is now going on, and immidiattly power down, again and again.
I don't know anymore what i have to do, even flashing a new rom don't seems to work.

Same problem to me, huawei mate 8. I had to come back to 14.5
Enviado desde mi HUAWEI NXT-L29 mediante Tapatalk

For anyone with bootloop issues, try grabbing a logcat when the device is bootlooping and then upload that together with the Magisk debug log (you can pull it from /data/adb/).

Im currently "Frozen" on the Carrier logo screen on my European S8, It does normally stay on this for a while, but it doesnt normally take THIS LONG. its been running for a good 10 mins.
The blue "Notification" light is glashing very lightly from a full brightness to slightly less bright on loop.
Its stupid I did not backup, and I REALLY REALLY need this phone to boot, I have a multi-asset cryptocurrency wallet on it tied to around 30k and I dont know if I have the privatekeys etc backed up!!!
Edit: For my S8, the only way I could shutdown is the volume down and power "Quick REBOOT" and the only way I could have it load the hotkey for recovery was doiung VOLUME DOWN + VOLUME UP (part of the hotkey for rec mode) + POWER BUTTON essentially just have 1 of the keys pressed and ready, once it starts rebooting asap press and hold bixby and let go of power and volume down and got into it. Im making a full backup in my broken state just incase I can recover my cryptocurrency using it.
Update on my situation!
So I used Magisk uninstaller and flashed it via twrp, cleared the dalvik cache by swiping, then rebooted system, it looped at the first screen where it says samsung s8 powered by android.
I went back into Magisk and saw it detected the boot image to be Stock and Magisk isnt installed, so that means one thing, Boot image is ****ed. So I LUCKILY had a full backup from 2 months ago from before I did Xposed I think, so I recovered only Boot Image from it and now im able to boot again without Magisk or Root.
Im going to install Magisk v14 again until I hear good word that possible issues are resolved.

Same thing on Honor 8 when I updated via MM > bootloop
Uninstaller didn't worked > bootloop
I backup with old twrp nandroid backup ^^
Tried again flashed v15 via twrp > bootloop
Tried with v14.6 > bootloop
Can't anymore install/root Magisk :'( :'(
Someone have a older of 14.6 version maybe I could try

remi13014 said:
Same thing on Honor 8 when I updated via MM > bootloop
Uninstaller didn't worked > bootloop
I backup with old twrp nandroid backup ^^
Tried again flashed v15 via twrp > bootloop
Tried with v14.6 > bootloop
Can't anymore install/root Magisk :'( :'(
Someone have a older of 14.6 version maybe I could try
Click to expand...
Click to collapse
v14.0 was the last version of Magisk that worked on my S8, the versions from there on were probs caused with the pizelization changes or whatever, so try that, and yeah man same **** happening with me :/

14.0 to 15.0 on my LG v20 is now booting into recovery. I can boot the system from there, but the process takes about 15 min or more.
I'm assuming this is most likely user error, since I'm a bit rusty at this.

Norma Stitz said:
14.0 to 15.0 on my LG v20 is now booting into recovery. I can boot the system from there, but the process takes about 15 min or more.
I'm assuming this is most likely user error, since I'm a bit rusty at this.
Click to expand...
Click to collapse
You were stuck on a carrier screen for 15~mins?

I have the same problem, after the update my P10lite had a generic ID and after reinstalling it is now stuck on erecovery.

I had the same problem. I re-flashed boot.img from my rom(Stock) and verified that it booted, then reflashed TWRP recovery and finally flashed Magisk 15 from TWRP and now the phone is fine again.

magisk 15 on oneplus 3t open beta 19 (oreo) working fine. v14 was giving reboots. i suggest you all to try latest unofficial magisk version.

remi13014 said:
Same thing on Honor 8 when I updated via MM > bootloop
Uninstaller didn't worked > bootloop
I backup with old twrp nandroid backup ^^
Tried again flashed v15 via twrp > bootloop
Tried with v14.6 > bootloop
Can't anymore install/root Magisk :'( :'(
Someone have a older of 14.6 version maybe I could try
Click to expand...
Click to collapse
As far as I know 14.6 isnt "Stable" version still, so I recommend trying v14.0
You should uninstall Magisk completely and then try see if your system boots (it will still take a while even though u uninstalled) once you do that and if you can boot fine, then try install v14 if you are stuck or boot looping, then your boot image could be ****ed/corrupt, so I recommend trying to install a backup of boot image only, you should have a backup in TWRP or something And you can select to recover only boot image, try that it sorted me out!

imPRAGMA said:
You were stuck on a carrier screen for 15~mins?
Click to expand...
Click to collapse
Yes. AT&T screen. 12-18 minutes, several consecutive times before I eventually fat fingered it into a kernel crash.
Currently restored and running fine at 14.0.
edit: still booting slow.
edit 2:
uninstalled manager, flashed uninstaller (didn't reboot), flashed v15.0.
Working great now.

Norma Stitz said:
Yes. AT&T screen. 12-18 minutes, several consecutive times before I eventually fat fingered it into a kernel crash.
Currently restored and running fine at 14.0.
Click to expand...
Click to collapse
Yeah your on the same issue I have where v15.0 simply wont go past carrier screen seems like you went past it fine after 18 mins, but I still have not, either im too impatient or it flat out is buggy for S8 Exynos.

Root SM-M405F (Galaxy M40)

Read all the Instructions very carefully, as missing even a single steps cause bootloop.
1. Unlocking Bootloader
Allow bootloader unlocking in Developer options → OEM unlocking
Power off your device. Press Volume Up + Volume Down and plug in your device to a PC to boot into download mode
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Just when you think the bootloader is unlocked, surprise surprise, it is actually not! Samsung introduced VaultKeeper in the system, meaning the bootloader will reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to internet in the setup!
Enable developer options, and confirm that the OEM unlocking option exists and grayed out!
2. Before Installing Magisk
Installing Magisk WILL trip KNOX
Installing Magisk for the first time REQUIRES a full data wipe, backup before continue
You have to have your bootloader unlocked before following the instructions
After installing Magisk, you can directly upgrade Magisk within Magisk Manager without an issue.
3. Flashing Magisk:
Download the firmware for SM-M405F
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Install the latest Magisk Manager
In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
Copy the tar file to your PC and boot your device to download mode.
Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options!
Magisk is now successfully flashed! But there are still several steps before you can properly use the device.
We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press Power + Volume Up to boot to recovery partition. Just as mentioned in the previous section, since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
In the stock recovery menu, use volume buttons to navigate through menus, and the power button to select the option. Select Wipe data/factory reset to wipe the data of the device.
This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press Power + Volume Up. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
The device will automatically reboot for the first time it boots. This is completely normal and done by design.
After the device is booted up, do the usual initial setup. The following steps will need internet connection.
You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Enjoy Root

Successfully rooted Galaxy M40
Thanks for the post. I have successfully rooted Galaxy M40 using magisk. Just one thing to add to the above post-- while copying patched ap from phone to pc use adb otherwise the flashing patched AP fails.

Ayan Chakraborty said:
Thanks for the post. I have successfully rooted Galaxy M40 using magisk. Just one thing to add to the above post-- while copying patched ap from phone to pc use adb otherwise the flashing patched AP fails.
Click to expand...
Click to collapse
I did not use Adb, it went smoothly for me. :good:

Enable 3CA for Rooted M40
Galaxy M40 uses LTE 2CA but the chipset supports 3CA. Can we enable it for Rooted M40?

Be careful doing this, since the latest Samsung firmware update in August it doesn't work anymore. You can root at first, but then every time you reboot the phone unroots... If you persist and do it again Samsung lock the phone for "security reasons" and you can't even reach the bootloader or recovery screens using the up / down buttons... Meaning you can't go back to stock firmware without taking your phone back to the store or sending for service, but of course you now no longer have warranty.

awsmanks said:
I did not use Adb, it went smoothly for me. :good:
Click to expand...
Click to collapse
This method will work for samsung a60 with his own firmware? Its the china better version of m40, i think i'll try this method

Rooted Successfully.
I had to flash twice since it did not boot into the stock recovery first time and messed with root I presume. second time it went perfectly and manually installed magisk manager. later magisk manager did some setups and rebooted my system.
Thanks Dev.
waiting for TWRP

rajeshca911 said:
Rooted Successfully.
I had to flash twice since it did not boot into the stock recovery first time and messed with root I presume. second time it went perfectly and manually installed magisk manager. later magisk manager did some setups and rebooted my system.
Thanks Dev.
waiting for TWRP
Click to expand...
Click to collapse
So this the new update it works?

Scorpio02 said:
This method will work for samsung a60 with his own firmware? Its the china better version of m40, i think i'll try this method
Click to expand...
Click to collapse
The A60 and the M40 are identical, it's not the "china better version" lol, it's just 90 USD more expensive because Chinese people have more money. It's literally identical down to the microchips inside.

Scorpio02 said:
So this the new update it works?
Click to expand...
Click to collapse
I think that I flashed on latest firmware AP_M405FDDU1ASF2_CL16060793_QB24248847_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS9.tar
Android Pie
Magisk 19.3
Magisk Manager 7.3.2
everything works perfectly except that annoying message on the boot screen
Here are my screenshots
View attachment 4807915
{
"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"
}
View attachment 4807917

I've uploaded the latest firmware file to Mega for anyone who doesn't want to wait 10 years for it to download from the snail-speed Samsung Firmware website:
https://mega.nz/#!T1sBka7B!iP8Ub8xbmO4ppa1CJg5vh4dWk_Vh-KjnPM6M6VjiqCc
Feel free to check the MD5 hashes, zero changes.

Theseusperse said:
Be careful doing this, since the latest Samsung firmware update in August it doesn't work anymore. You can root at first, but then every time you reboot the phone unroots... If you persist and do it again Samsung lock the phone for "security reasons" and you can't even reach the bootloader or recovery screens using the up / down buttons... Meaning you can't go back to stock firmware without taking your phone back to the store or sending for service, but of course you now no longer have warranty.
Click to expand...
Click to collapse
I rooted my phone yesterday, today I rebooted my phone. and pfff it is gone.
this rooting procedure is not persistent
Waiting for a stable root method
now I am neither on ofw nor on rooted firmware

rajeshca911 said:
I rooted my phone yesterday, today I rebooted my phone. and pfff it is gone.
this rooting procedure is not persistent
Waiting for a stable root method
now I am neither on ofw nor on rooted firmware
Click to expand...
Click to collapse
Yeah that was the same issue I was having, I'm using the Indian version of the firmware so I wonder if it just affects Indian models.
I did a lot of research and there's actually not just 5 international models but 7, some with a /DS on the end which appear to use different firmwares, and I wonder if that is the cause of the issue.
Anyway I found a temporary fix. Reset everything back to stock firmware, do the rooting as the guide shows on page 1, then ALWAYS reboot using root, either by installing or upgrading a new Magisk module, or updating your AdAway blacklist, or by using ADB Shell #Su... For some reason when you reboot like this it doesn't unroot the phone and everything stays fine. Also make sure you never ever press the "Okay continue" button that appears when the phone first starts and tells you the bootloader is unlocked, just wait a while and allow it to continue automatically.

Theseusperse said:
Yeah that was the same issue I was having, I'm using the Indian version of the firmware so I wonder if it just affects Indian models.
I did a lot of research and there's actually not just 5 international models but 7, some with a /DS on the end which appear to use different firmwares, and I wonder if that is the cause of the issue.
Anyway I found a temporary fix. Reset everything back to stock firmware, do the rooting as the guide shows on page 1, then ALWAYS reboot using root, either by installing or upgrading a new Magisk module, or updating your AdAway blacklist, or by using ADB Shell #Su... For some reason when you reboot like this it doesn't unroot the phone and everything stays fine. Also make sure you never ever press the "Okay continue" button that appears when the phone first starts and tells you the bootloader is unlocked, just wait a while and allow it to continue automatically.
Click to expand...
Click to collapse
Thanks Theseusperse, I will follow that. and can u suggest me easy way to port twrp? I tried carlive image kitchen however when i flashed it not only reboots into stock rom but also shrinked my internal space to 16 GB. To Revert this effect I had to flash stock rom again using Odin ( only odin other tools failed) . Please let me know if there is any safe porting Recovery

rajeshca911 said:
Thanks Theseusperse, I will follow that. and can u suggest me easy way to port twrp? I tried carlive image kitchen however when i flashed it not only reboots into stock rom but also shrinked my internal space to 16 GB. To Revert this effect I had to flash stock rom again using Odin ( only odin other tools failed) . Please let me know if there is any safe porting Recovery
Click to expand...
Click to collapse
There won't be any port of TWRP for a long time, Samsung has to release the source code for the phone first. Based on the Galaxy A series that was released in May this year, they just got their source code last week and the TWRP porting community literally kicked off in the past few days, so we'll probably have to wait some months. I'd estimate November sometime.
I'm excited for when it finally does happen though, I absolutely hate the stock Samsung software and want pure Google, even if it means a GSI rom.
Our phone is actually 100% identical to the Samsung Galaxy A60, so it's possible any TWRP ports made for that device would work, but so far the ones I've tried have all failed and resulted in the same effects you experienced.

SIZE=1]---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------[/SIZE]
[/COLOR]
Theseusperse said:
There won't be any port of TWRP for a long time, Samsung has to release the source code for the phone first. Based on the Galaxy A series that was released in May this year, they just got their source code last week and the TWRP porting community literally kicked off in the past few days, so we'll probably have to wait some months. I'd estimate November sometime.
I'm excited for when it finally does happen though, I absolutely hate the stock Samsung software and want pure Google, even if it means a GSI rom.
Our phone is actually 100% identical to the Samsung Galaxy A60, so it's possible any TWRP ports made for that device would work, but so far the ones I've tried have all failed and resulted in the same effects you experienced.
Click to expand...
Click to collapse
Im excited to hear that A60 recovery might work on M40 any ways me either hate to be on stock rom. I got habituated to the root and custom roms. Hope A60 source works for M40 . Please do update me if anything that kind of miracle happens. Thanks in advance Brother

rajeshca911 said:
I rooted my phone yesterday, today I rebooted my phone. and pfff it is gone.
this rooting procedure is not persistent
Waiting for a stable root method
now I am neither on ofw nor on rooted firmware
Click to expand...
Click to collapse
To prevent loosing magisk root after reboot. NEVER REBOOT NORMALLY but Reboot it via Magisk or Fully Power Off then Turn Power On.

redymedan said:
To prevent loosing magisk root after reboot. NEVER REBOOT NORMALLY but Reboot it via Magisk or Fully Power Off then Turn Power On.
Click to expand...
Click to collapse
Can i reflash again 0n same rom without loosing data ??
Sent from my SM-M405F using Tapatalk

rajeshca911 said:
Can i reflash again 0n same rom without loosing data ??
Sent from my SM-M405F using Tapatalk
Click to expand...
Click to collapse
No, never ever do this, it will shrink your data partition and there's no way to ever fix it, even with a total system restore or using manufacturer tools.

Theseusperse said:
No, never ever do this, it will shrink your data partition and there's no way to ever fix it, even with a total system restore or using manufacturer tools.
Click to expand...
Click to collapse
Too late, I already did that and it shrieked my devices storage to 16Gb first time and 32 gb on second flash. But It got fixed with Odin repartition. Dont worry It is fixable
Sent from my SM-M405F using Tapatalk