Database Develop

note 3 bootloop

I had Note 3 safestrap installed.
Factory wiped and I flashed PureRom Ce over S5 experience rom on kit kit 4.4 and reboot.
The note 3 will not start into boot logo but appears as Galaxy note 3 with unlocked icon and nothing else. Tried to boot me to recovery it did take me to stock recovery. I hit factory reset and cache and problem still the same.
Any ideas? if problem do not solved, all I do to hit up odin to flash new firmware?

LeonKnight12 said:
I had Note 3 safestrap installed.
Factory wiped and I flashed PureRom Ce over S5 experience rom on kit kit 4.4 and reboot.
The note 3 will not start into boot logo but appears as Galaxy note 3 with unlocked icon and nothing else. Tried to boot me to recovery it did take me to stock recovery. I hit factory reset and cache and problem still the same.
Any ideas? if problem do not solved, all I do to hit up odin to flash new firmware?
Click to expand...
Click to collapse
Seems like you formatted sd in ss, did you reboot normally or you pressed vol up menu and power? Try to reboot, if ss doesn't show up you may have to revert to mj5.

posersk8r said:
Seems like you formatted sd in ss, did you reboot normally or you pressed vol up menu and power? Try to reboot, if ss doesn't show up you may have to revert to mj5.
Click to expand...
Click to collapse
You are right, I formatted it by pc. I thought everything had covered. The ss I had was installed but recovery did not "recovery not active" someone claimed it was bug. So I rebooted got ss then flashed purerom on kk, and this was happening right after reboot. I gonna have to look in thread about mj5 you mentioned. Download mode working fine and stock recovery working fine. Ugh I need to get home and have this fixed. I'm at work stuck with boot looping note 3. Hope to get this fixed tonight.

LeonKnight12 said:
You are right, I formatted it by pc. I thought everything had covered. The ss I had was installed but recovery did not "recovery not active" someone claimed it was bug. So I rebooted got ss then flashed purerom on kk, and this was happening right after reboot. I gonna have to look in thread about mj5 you mentioned. Download mode working fine and stock recovery working fine. Ugh I need to get home and have this fixed. I'm at work stuck with boot looping note 3. Hope to get this fixed tonight.
Click to expand...
Click to collapse
"Recovery not active" means you are using the stock slot. Yeah just follow the steps in the mj5 restore done that numerous times and it always brought me back. Hope you get that note 3 firing again.

Thanks I got my note 3 back to life using mj5 restore. Problem solved.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Stuck on Boot Loop
posersk8r said:
Seems like you formatted sd in ss, did you reboot normally or you pressed vol up menu and power? Try to reboot, if ss doesn't show up you may have to revert to mj5.
Click to expand...
Click to collapse
Hey im in need of some desperate help, so In safestrap i activated one of the rom slots and left alone the stock rom slot, after i created and activated a rom slot, i intalled lollipop rooted from Walter White, then now i've been stuck on "Samsung GALAXY Note 3" logo withiout the lock at the bottom for the past hour, how do i get back in to safestrap?!! need to go back to stock rom! please help!

Can't enter recovery mode???

I can't seem to figure out how to enter into recovery mode on my T-Mobile G4. It's running everything completely stock. I have tried holding power button and volume up until the logo comes on and releasing both buttons and then immediately holding them both down again waiting.. and nothing happens. I've even tried waiting for one second after I initially release to hold them down again. Same outcome. It always just boots back up into Android. I have tried volume down instead.. Nothing. Can someone please show me how to boot into recovery mode? Again, running stock rom.

I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.

Demati said:
I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.
Click to expand...
Click to collapse
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..

From the T-mobile website: https://support.t-mobile.com/docs/DOC-21911

stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.

That's not what I'm talking about. That's talking about factory resetting your phone with the hardware keys. I'm talking about entering recovery mode (kinda like the bios of the phone) using the hardware keys.. It's different.

Demati said:
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.
Click to expand...
Click to collapse
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.

stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
stringz90 said:
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.
Click to expand...
Click to collapse
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?

Demati said:
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?
Click to expand...
Click to collapse
Alright.. I guess, I'll have to try that, but first is there any way to do a backup of some sort in case I have to go back to stock rom rooted? I got my G4 about a month ago and haven't done much research on rooting this specific device. I haven't had a high end phone with rooting and rom options in a long time. The last phone I had a chance to root and install cool custom roms on was a Samsung Galaxy S2. If you can guide me in the right direction I'd appreciate it. I guess I have to start from square one again. In the past I remember that in order to go back to completely stock you had to have a usb jib to reset the flash counter. Is it the same for this case? I welcome anyone's helpful input. Thanks, everyone.

Bricked my myphone uno using Android One Toolkit

After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?

t-rayms said:
After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?
Click to expand...
Click to collapse
If you could tell us more clearly about what did you do actually and which instructions did you followed?

DNA_Uncut said:
If you could tell us more clearly about what did you do actually and which instructions did you followed?
Click to expand...
Click to collapse
i followed(or tried to) the instructions from the site of androidmtk with topic
"how to root android one devices easily"
sorry but system will not let me paste the actual link.
Process involved the use of android one toolkit.
and now my phone no longer boots. Stuck with those 4 animated circles. I have to remove the battery to get out of that screen. But no matter what i did, isn't there a way to just install android? Like installing windows on a blank hard drive? Start from scratch? Loss of data is not a factor

t-rayms said:
i followed(or tried to) the instructions from the site of androidmtk with topic
"how to root android one devices easily"
sorry but system will not let me paste the actual link.
Process involved the use of android one toolkit.
and now my phone no longer boots. Stuck with those 4 animated circles. I have to remove the battery to get out of that screen. But no matter what i did, isn't there a way to just install android? Like installing windows on a blank hard drive? Start from scratch? Loss of data is not a factor
Click to expand...
Click to collapse
Just follow the thread
http://forum.xda-developers.com/dream-uno/development/stock-rom-spice-dream-uno-mi498-t2915844
Download ROM (from the same thread)
http://forum.xda-developers.com/showpost.php?p=61588267&postcount=23
You should get back to stock kitkat (if you follow the instructions as explained). Once you get back your phone to working. Install ota updates you receive that will get you to stock 6.01

t-rayms said:
After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?
Click to expand...
Click to collapse
You don't need to go back on kitkat as DNA uncut says .....your device is running on which recovery ??

devil anand said:
You don't need to go back on kitkat as DNA uncut says .....your device is running on which recovery ??
Click to expand...
Click to collapse
im sorry but i dont know what "recovery" is. The phone is also no longer turning on so i cant get that info. But im ok with trying kitkat and if the flashing of the ROM works, at least ill have a working phone. And go from there and experiment some more to get the most out of the device.

When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
---------- Post added at 03:58 AM ---------- Previous post was at 03:49 AM ----------
t-rayms said:
im sorry but i dont know what "recovery" is. The phone is also no longer turning on so i cant get that info. But im ok with trying kitkat and if the flashing of the ROM works, at least ill have a working phone. And go from there and experiment some more to get the most out of the device.
Click to expand...
Click to collapse
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see

DNA_Uncut said:
Just follow the thread
http://forum.xda-developers.com/dream-uno/development/stock-rom-spice-dream-uno-mi498-t2915844
Download ROM (from the same thread)
http://forum.xda-developers.com/showpost.php?p=61588267&postcount=23
You should get back to stock kitkat (if you follow the instructions as explained). Once you get back your phone to working. Install ota updates you receive that will get you to stock 6.01
Click to expand...
Click to collapse
i installed the Android CDC Driver. DL the SP Flash Tool and the custom ROM. Rebooted the PC. Ran the SP Flash Tool. The final stage where i click on DL and connect my phone, nothing happens. The scrolling progress bar at the bottom of the flash tool doesnt start. With or w/o batteries in the phone. What do i do next?

devil anand said:
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
---------- Post added at 03:58 AM ---------- Previous post was at 03:49 AM ----------
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
Click to expand...
Click to collapse
when i selected the recovery option, the next screen is a picture of the android robot lying face up. With its body panel door open with red triangle with black exclamation markm, "No command" prompt

t-rayms said:
when i selected the recovery option, the next screen is a picture of the android robot lying face up. With its body panel door open with red triangle with black exclamation markm, "No command" prompt
Click to expand...
Click to collapse
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Link - kernel- http://www.thunderzap.in/downloads/
SuperSU - https://download.chainfire.eu/741/SuperSU?_e_pi_=7,PAGE_ID10,5223979215

devil anand said:
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Link - kernel- http://www.thunderzap.in/downloads/
SuperSU - https://download.chainfire.eu/741/SuperSU?_e_pi_=7,PAGE_ID10,5223979215
Click to expand...
Click to collapse
great. thanks. it worked. still cant believe it. But thank you very very very much.

t-rayms said:
great. thanks. it worked. still cant believe it. But thank you very very very much.
Click to expand...
Click to collapse
Just hit thanks!!
I went to Android mtk website ...then I knew where was the problem.
Note : SuperSU zip is used to root a phone via custom recovery (twrp,philzz) ...but in marshmallow you can't root your phone just by installing SuperSU zip ....you need to install a custom *kernel* first ....remember next time??

devil anand said:
Just hit thanks!!
I went to Android mtk website ...then I knew where was the problem.
Note : SuperSU zip is used to root a phone via custom recovery (twrp,philzz) ...but in marshmallow you can't root your phone just by installing SuperSU zip ....you need to install a custom *kernel* first ....remember next time
Click to expand...
Click to collapse
i take it that this step Then tap on wipe option and then factory reset and confirm it. fixed the bricking of the phone
and these steps After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
rooted the phone right?
One other thing is, whenever theres a system update, during the rebooting it does an error and i have to remove battery to restart the phone. Does rooting the phone cause updates not to work?

t-rayms said:
i take it that this step Then tap on wipe option and then factory reset and confirm it. fixed the bricking of the phone
and these steps After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
rooted the phone right?
One other thing is, whenever theres a system update, during the rebooting it does an error and i have to remove battery to restart the phone. Does rooting the phone cause updates not to work?
Click to expand...
Click to collapse
You took a bit ....if you have rebooted your phone after just factory reset .....you may have got bootloop again.....(stuck on boot animation).
About your second problem ....
When the error happens in between these steps of installation .......you tap on reboot and install and your phone goes to recovery and after successful installation your reboots .
What's the error ??
Yeah rooting your phone changes system which causes problem while installation of the original update...??

devil anand said:
You took a bit ....if you have rebooted your phone after just factory reset .....you may have got bootloop again.....(stuck on boot animation).
About your second problem ....
When the error happens in between these steps of installation .......you tap on reboot and install and your phone goes to recovery and after successful installation your reboots .
What's the error ??
Yeah rooting your phone changes system which causes problem while installation of the original update...
Click to expand...
Click to collapse
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.

t-rayms said:
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.
Click to expand...
Click to collapse
Just unroot your phone and try updating again !!!??

devil anand said:
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Click to expand...
Click to collapse
It worked for me too, but now I can`t update SuperSU.
Update from OS failed, from TWRP gives bootloop.
I`m on CM13 SNAPSHOT.
... also front camera cant take picture, but preview works ok.

Johnny_16 said:
It worked for me too, but now I can`t update SuperSU.
Update from OS failed, from TWRP gives bootloop.
I`m on CM13 SNAPSHOT.
... also front camera cant take picture, but preview works ok.
Click to expand...
Click to collapse
What's the need of updating SuperSU ..,...
Use Google camera ....
Sent from my A1 using XDA-Developers mobile app

t-rayms said:
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.
Click to expand...
Click to collapse
You've root? And which update do you wanna install on your phone!?
Just tell me what's your build number.. I'll help ya out.

HELP
My cousins Myphone Uno is not turning on when pressing the power button, but if I put in a charge the screen turns on after a few minutes showing the battery but I don't know if it is charging. after a minute the display will go out and the screen flashes a once or twice then off and screen turns on and display the battery it will be on a loop, I can still get to boot option when screen flashes starts,
it shows:
[Recovery Mode]
[Fastboot Mode]
[Normal Boot]
[Normal Boot +ftrace]
[Normal slub debug off]
but when I select any options or not to ,the phone will turn off. Can you help me find a way to make this phone work again? thank you in advance!
PS: If I connect it in my PC it wasn't detected and the the loop will go on and on.
Usb debugging mode is also turned off

Bootlooping

I have a Samsung galaxy note 9 sm,-n960f with TWRP 3.2.3 Cowrite unofficial recovery. I backed up my phone. But when I tried to restore the backups I got an error message. So I decided to TWRP 3.3.1. It was successfully flashed. But when I booted into recovery, the phone just keeps recycling the flash screen without going into recovery mode. It has been doing this for the past two hours. Could someone please tell me what to do. I can't stop it. Please help.

Baluki2017 said:
I have a Samsung galaxy note 9 sm,-n960f with TWRP 3.2.3 Cowrite unofficial recovery. I backed up my phone. But when I tried to restore the backups I got an error message. So I decided to TWRP 3.3.1. It was successfully flashed. But when I booted into recovery, the phone just keeps recycling the flash screen without going into recovery mode. It has been doing this for the past two hours. Could someone please tell me what to do. I can't stop it. Please help.
Click to expand...
Click to collapse
prepair to go back to dl mode to flash back twrp 3.2.3 tar with Odin.
hold bixby and vol down while plugging usb from computer in the phone.
time yourself that when see/feel the phone reboot to plug usb at that moment( while holding bxby + vol down)
btw did u flash twrp 3.3.1 using image option in twrp or did you flash it with odin?

I flashed it in trwp.

Baluki2017 said:
I flashed it in trwp.
Click to expand...
Click to collapse
dont flash it in twrp. also you might have chosen the wrong target partition... did u remember selecting recovery or boot?

A million thanks to you. I got it working again. I did exactly what you said and it worked like a charm.
The main issue that got me into this problem is the backups I created with this recovery. Whenever I tried to install them, I get an error. Is there something that I'm doing wrong?
When I had my note 3, I never had this problem. Is there a bug in this 3.3.2 i unofficial recovery. Could you tell me what to include in my backups and what to include in my restore.
Thank you for your assistance.

Baluki2017 said:
A million thanks to you. I got it working again. I did exactly what you said and it worked like a charm.
The main issue that got me into this problem is the backups I created with this recovery. Whenever I tried to install them, I get an error. Is there something that I'm doing wrong?
When I had my note 3, I never had this problem. Is there a bug in this 3.3.2 i unofficial recovery. Could you tell me what to include in my backups and what to include in my restore.
Thank you for your assistance.
Click to expand...
Click to collapse
3.3.1 based twrps are pretty much betas if you ask me . stick to good old 3.2.3-0
also when backing up various partitions. skip "system image". so check box any or all others including system but no need to select "system image" its not needed and cant be restored anyways.

Thanks again. I will try that.

Hello my friend. I need your help again. I just got myself in a big mess. I did a full wipe in recovery. Before I restored the backups , I accidentally rebooted the phone and now I am stucck in a black circle and a small white symbol inside the top side of the black circle.
I tried booting into download mode.so that I could rry to refalas the recovery please help help me.
Tank

Baluki2017 said:
Hello my friend. I need your help again. I just got myself in a big mess. I did a full wipe in recovery. Before I restored the backups , I accidentally rebooted the phone and now I am stucck in a black circle and a small white symbol inside the top side of the black circle.
I tried booting into download mode.so that I could rry to refalas the recovery please help help me.
Tank
Click to expand...
Click to collapse
hold:
vol down + power
the instant you see or feel phone shutdown really quickly hold:
vol up + bixby + power
if u miss it try again. timing is key.

Ok. I will do that.
Thanks again.

Does installing any modules is actually safe?

Hi there!
Just a quick question. Finally afer so much time since the actual update to emui 9.1 (Psmart Fig-lx1) Ive finally managed to get that **** done - i mean rooting that mother****er
From what I gathered if I want to reboot the phone I have to hold that power vol + button 'n 'stuff. So question remains simple.
**So if i would instal a magisk module and it reboots my phone - do I need to just hold that vol + button and the planet wont go boom, or is ther aleoso some specific stuff You need to co?
**Also - what does 'recovery mode option in Magisk Manager means?
Cheers!

Why would you have to hold the vol + button to reboot at all? That's not normal.
Sent from my LG-US998 using Tapatalk

kenbo111 said:
Why would you have to hold the vol + button to reboot at all? That's not normal.
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
A recent method on installing magisk trough a patched recovery image require exacly that. And it's not the end. When You boot normally no buttons - You've got non rooted system (without magisk)
When You keep Vol+ till splash screen You've got system with magisk (full root)
And when You keep that VoL allll the way - You suppose to boot into recovery.
I too don't know how they pulled this off but just in case something wouild go wronga after instalation of the meodules I'd like to know in advence

That's wierd! I've never heard of that before
Sent from my LG-US998 using Tapatalk

kenbo111 said:
That's wierd! I've never heard of that before.
Click to expand...
Click to collapse
It's uncommon, but not unheard of. Rebooting that way be needed for devices where a Magisk patched boot image is swapped with the recovery image (since the modified boot image couldn't be put in place of the original, untampered one for some reason). In such cases, if you reboot to recovery, the Magisk modified boot image will be loaded instead of the recovery, which will lead to booting into a rooted ROM. This is how root also works for Samsung S9 and Note 9.

shadowstep said:
It's uncommon, but not unheard of. Rebooting that way be needed for devices where a Magisk patched boot image is swapped with the recovery image (since the modified boot image couldn't be put in place of the original, untampered one for some reason). In such cases, if you reboot to recovery, the Magisk modified boot image will be loaded instead of the recovery, which will lead to booting into a rooted ROM. This is how root also works for Samsung S9 and Note 9.
Click to expand...
Click to collapse
That sounds both incredibly annoying and tedious but also quite handy when it comes to recovering from bootloops when you aren't near a PC ?
Sent from my Pixel 3a XL using XDA Labs

Skittles9823 said:
That sounds both incredibly annoying and tedious but also quite handy when it comes to recovering from bootloops when you aren't near a PC ?
Click to expand...
Click to collapse
Yet, it is. That's why I'll never buy devices that can't be easily rooted. I forgot to add, since the images are swapped (original boot becomes recovery and recovery becomes Magisk patched boot), a normal reboot would lead to booting to recovery everytime and rebooting to recovery (either by a key combo or from the ROM itself) is needed to boot to system. Good times.

shadowstep said:
Yet, it is. That's why I'll never buy devices that can't be easily rooted. I forgot to add, since the images are swapped (original boot becomes recovery and recovery becomes Magisk patched boot), a normal reboot would lead to booting to recovery everytime and rebooting to recovery (either by a key combo or from the ROM itself) is needed to boot to system. Good times.
Click to expand...
Click to collapse
Ahh my brain hurts lmao.
I thought it would boot into an unrooted system if not using the recovery shortcut. Yea that does sound irritating.

Skittles9823 said:
Ahh my brain hurts lmao.
I thought it would boot into an unrooted system if not using the recovery shortcut. Yea that does sound irritating.
Click to expand...
Click to collapse
I am sure, lol. Also, if it boots to an unrooted system if not using the recovery shortcut and to a rooted system if using that recovery shortcut, how do you access recovery? Be glad you have a much more root-friendly device.

shadowstep said:
Also, if it boots to an unrooted system if not using the recovery shortcut and to a rooted system if using that recovery shortcut, how do you access recovery? Be glad you have a much more root-friendly device.
Click to expand...
Click to collapse
Haha yea, that's true.
Sent from my Pixel 3a XL using XDA Labs

shadowstep said:
Yet, it is. That's why I'll never buy devices that can't be easily rooted. I forgot to add, since the images are swapped (original boot becomes recovery and recovery becomes Magisk patched boot), a normal reboot would lead to booting to recovery everytime and rebooting to recovery (either by a key combo or from the ROM itself) is needed to boot to system. Good times.
Click to expand...
Click to collapse
In fact, the images are not swapped (at least on S10). If you hold the Vol key long enough, the recovery kernel will boot the recovery system, and if you release it, it'll boot android. So, a rooted system runs on the recovery kernel.

Keule-T said:
In fact, the images are not swapped (at least on S10). If you hold the Vol key long enough, the recovery kernel will boot the recovery system, and if you release it, it'll boot android. So, a rooted system runs on the recovery kernel.
Click to expand...
Click to collapse
Not sure about the S10, but they are definitely swapped for S9. More information can be taken from this XDA article (and the thread links referenced in it). :good:

given nice contidions, any phone can break just by using magisk modules that do tricky stuff to ur image. and since that applies on any magisk module for a varius of reasons, wellp there is no "safe" module. under certain circumstances every module can break **** down.