Note 4 - failed root, stuck in bootloop - Verizon Galaxy Note 4 Q&A, Help & Troubleshooting

All,
Tried to root Verizon Note 4 following instructions on this site: galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4
After getting root I got to the point where I flashed the system-only ROM and Odin reported success. On reboot with TWRP that it got stuck in boot loop.
Downloaded full firmware ROM and flashed it in the hopes of starting from scratch and now TWRP is gone and it's still stuck in boot loop.
Factory wipe didn't work. Up-vol - Home - Power displays the factory recover screen.
Any ideas on how to get it back to factory or some other working firmware?
-Thx

SOLVED
Found a factory ROM for the N910V and upgraded Odin to latest version. Started in download mode, flashed ROM with Odin, all is well. I think I had a corrupted ROM that didn't flash.
Now that I've recovered this thing successfully I'll have another go at rooting it so I can get rid of the bloat for good. I'll probably be back with another tale of misery after bricking it...

spumco said:
All,
Tried to root Verizon Note 4 following instructions on this site: galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4
After getting root I got to the point where I flashed the system-only ROM and Odin reported success. On reboot with TWRP that it got stuck in boot loop.
Downloaded full firmware ROM and flashed it in the hopes of starting from scratch and now TWRP is gone and it's still stuck in boot loop.
Factory wipe didn't work. Up-vol - Home - Power displays the factory recover screen.
Any ideas on how to get it back to factory or some other working firmware?
-Thx
Click to expand...
Click to collapse
Are you still stuck?

Sort-of. I found a clean factory MM ROM that fixed everything and the phone is live and happy. ROM N910VVRU2CPG2.
However, I'm unable to root it now. Searched a number of threads and have not been able to find a KingOroot or TWRP that will work. Nor can I downgrade to 5.1.1 and start from there.
So working phone, but no root and all bloatware intact. If you (or anyone else) has a idiot-friendly solution I'm all ears.

spumco said:
Sort-of. I found a clean factory MM ROM that fixed everything and the phone is live and happy. ROM N910VVRU2CPG2.
However, I'm unable to root it now. Searched a number of threads and have not been able to find a KingOroot or TWRP that will work. Nor can I downgrade to 5.1.1 and start from there.
So working phone, but no root and all bloatware intact. If you (or anyone else) has a idiot-friendly solution I'm all ears.
Click to expand...
Click to collapse
It wont't let you downgrade? Had you pulled the sd card?
---------- Post added at 03:01 PM ---------- Previous post was at 02:50 PM ----------
What happens when you flash 5.1.1?

ziggy71 said:
It wont't let you downgrade? Had you pulled the sd card?
---------- Post added at 03:01 PM ---------- Previous post was at 02:50 PM ----------
What happens when you flash 5.1.1?
Click to expand...
Click to collapse
Doesn't matter what version ROM, Odin now fails to write. And I cant get Kingoroot to do the temp root, so doing the Console/ADB trick right after temp root doesn't work.
PC version of Kingoroot doesn't work either.
I'm sure there's a way to break in to this thing, but I'm such a novice it's not even funny.

Well the exploit is in 5.1.1. So that is what you need to be on. Try a different version of odin, try a factory reset on the phone
https://androidfilehost.com/?fid=24411628330026105
That's the full 5.1.1. Install that and get your phone going. If you can't get that installed, then you can't root

ziggy71 said:
Well the exploit is in 5.1.1. So that is what you need to be on. Try a different version of odin, try a factory reset on the phone
https://androidfilehost.com/?fid=24411628330026105
That's the full 5.1.1. Install that and get your phone going. If you can't get that installed, then you can't root
Click to expand...
Click to collapse
Thanks much. I'll D/L it and have a go. Will report back either way.

SUCCESS!
The full 5.1.1 install was successfully loaded. I then followed the root exploit found on this forum (I think it was the 'simplified' thread) and Kingroot worked the 2nd try. The cleaned up stock ROM linked in the rooting thread was also loaded, along with TWRP.
Thanks a ton for the assistance!

Glad it worked out for you.

Related

Need help unbricking T-mobile N900TUVUBMI7

Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.
re: md5 error
Silvist said:
Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.
Click to expand...
Click to collapse
Before doing anything else you need to re-download the TAR.MD5 firmware.
If you get MD5 errors it simply means that for some reason the download
had an error in it (checksum error).
You need to have a error free download of the TAR.MD5 firmware in order
to solve the issues you are having. Your phone is NOT bricked at all and all
it needs is a error free TAR.MD5 file to flash with odin and your phone will
work perfectly. You should never flash a TAR.MD5 file which has errors.
Your problem has nothing to do with the versions of the firmwares like 4.4.2
and or 4.3 you are trying to flash, it all has to do with errors during the actual
download process of the TAR.MD5 file.
Good luck!
Thank you for replying!
So what should I look for in terms of flashing then? Just full stock of the t-mobile US version?
Reason I asked is because I'd downloaded about 15 different ones from all different sources, and only that one didn't have the issue. Should I try to flash through twrp over Odin?
Edit:
Like for instance I tried the one from here:
http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398
This was the only one that worked actually. Though after I flash it with odin it just shows the samsung logo with "recovery booting" in the top left corner.
Wow..holy crap after like attempt number 40 with the same flashing in odin it actually booted up. That's just crazy lol.
Call me to un brick your phone
HEY CALL ME TO UNBRICK YOUR PHONE AM A REPAIR SHOP IF YOU MAIL ME THE PHONE I COULD FIX IT FOR A SMALL FEE [email protected] HAVE A GOOS DAY :fingers-crossed:
Silvist said:
Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.
Click to expand...
Click to collapse
For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
---------- Post added at 06:18 PM ---------- Previous post was at 06:10 PM ----------
blu422 said:
For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
Click to expand...
Click to collapse
Scratch that. This is what I believe happened. The way CF Auto-root works is it roots through a temporary custom recovery I believe. What happened is during the process something went wrong and the phone ended up with both a corrupted system and a corrupted recovery. You need to flash the stock tar to fix both then factory reset to make it boot the rest of the way. Again this is just for future reference with more people running into this problem... I do realize OP already got helped.
blu422 said:
For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
---------- Post added at 06:18 PM ---------- Previous post was at 06:10 PM ----------
Scratch that. This is what I believe happened. The way CF Auto-root works is it roots through a temporary custom recovery I believe. What happened is during the process something went wrong and the phone ended up with both a corrupted system and a corrupted recovery. You need to flash the stock tar to fix both then factory reset to make it boot the rest of the way. Again this is just for future reference with more people running into this problem... I do realize OP already got helped.
Click to expand...
Click to collapse
I always ODIN flash the newest firmware, let the phone boot up, then I just ODIN flash TWRP... and then in recovery I flash my personnel rom and flash SU from chainfire...
then I just install busybox which I have a copy of all the on my sdcard, a folder I call apk files.... then I install titanium backup and restore my apps.. all done in less then 10 minutes...
when ever u think u have a problem, flash the firmware your on, or the newest, that should always fix any issues.. I have all of the versions on my site, and stock odex roms...
Silvist said:
Thank you for replying!
So what should I look for in terms of flashing then? Just full stock of the t-mobile US version?
Reason I asked is because I'd downloaded about 15 different ones from all different sources, and only that one didn't have the issue. Should I try to flash through twrp over Odin?
Edit:
Like for instance I tried the one from here:
http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398
This was the only one that worked actually. Though after I flash it with odin it just shows the samsung logo with "recovery booting" in the top left corner.
Wow..holy crap after like attempt number 40 with the same flashing in odin it actually booted up. That's just crazy lol.
Click to expand...
Click to collapse
I'm actually having this exact issue how exactly did you fix it? mine just says booting recovery and then it loops and I've downloaded at least 4 different versions of the nf9 odin
xxjahasotoxx said:
I'm actually having this exact issue how exactly did you fix it? mine just says booting recovery and then it loops and I've downloaded at least 4 different versions of the nf9 odin
Click to expand...
Click to collapse
I just kept trying to flash to the stock image that's in the link in my post. It kept giving me md5 errors, so I re downloaded the file until it passed. I also ran odin as administrator, which helps. I used an older version of odin, 3.5 I believe.
Everything else I tried failed, like hemdall. I did attempt it, but it failed when I tried to flash through it. I'm not really familiar with it, just followed the guide on these forums. It can supposedly do more than even odin can do, that's if you can get it to work lol.

Tab Pro 12.2 - Unable to install TWRP - please help

I have a galaxy tab pro 12.2 wifi that I rooted via the CFauto-root (v2wifi) method. After a bit of a struggle getting it to root (it kept getting stuck at the cache.img step in odin, but finally worked when I tried it using a different PC even though the samsung drivers worked on both machines), I am unable to install TWRP using Flashify or via Odin.
Flashing via Odin seems to complete successfully, and it seems to flash successfully when I try through Flashify, but on reboot after either method, it just boots to the stock recovery. I've tried TWRP 2.8.0 and 2.8.5. I have tried running the root package again and it completes, but I cant seem to get around this issue.
Please help!
ahughes5 said:
I have a galaxy tab pro 12.2 wifi that I rooted via the CFauto-root (v2wifi) method. After a bit of a struggle getting it to root (it kept getting stuck at the cache.img step in odin, but finally worked when I tried it using a different PC even though the samsung drivers worked on both machines), I am unable to install TWRP using Flashify or via Odin.
Flashing via Odin seems to complete successfully, and it seems to flash successfully when I try through Flashify, but on reboot after either method, it just boots to the stock recovery. I've tried TWRP 2.8.0 and 2.8.5. I have tried running the root package again and it completes, but I cant seem to get around this issue.
Please help!
Click to expand...
Click to collapse
When your in odin, Untick auto reboot box. Then flash the twrp file in odin then force reboot by holding power,home,volume up and down buttons all at the same time till it reboots.
Thank you very much for the reply. Unfortunately that didn't seem to work either. It just locked on the samsung logo on reboot after trying that. Fortunately I was able to make some progress finally by flashing an old stock base (AND4), rerooting and flashing TWRP 2.8.0 from Odin. Even after going to the old stock base, flashing TWRP from Flashify wouldn't stick, and flashing 2.8.5 from Odin wouldn't either. It was only flashing 2.8.0 from Odin after going to the old base that worked. Never had so much trouble getting rooted and recovery on a device. Also a big thanks to Trav06 for getting a debloated stock rom for the 12.2. Flashed last night and its running well so far.
Thank you for the help!
ahughes5 said:
Thank you very much for the reply. Unfortunately that didn't seem to work either. It just locked on the samsung logo on reboot after trying that. Fortunately I was able to make some progress finally by flashing an old stock base (AND4), rerooting and flashing TWRP 2.8.0 from Odin. Even after going to the old stock base, flashing TWRP from Flashify wouldn't stick, and flashing 2.8.5 from Odin wouldn't either. It was only flashing 2.8.0 from Odin after going to the old base that worked. Never had so much trouble getting rooted and recovery on a device. Also a big thanks to Trav06 for getting a debloated stock rom for the 12.2. Flashed last night and its running well so far.
Thank you for the help!
Click to expand...
Click to collapse
Unfortunately I have the same experience as you. It just lokced on the T-900 screen. I end up reflashed a stock recovery with ODIN. I am seeking solution too.
I was finally able to get it working by flashing TWRP 2.8.0 via Odin 3.09 after flashing back to an old samsung base (pre-ANK1). I couldn't get TWRP 2.8.5 to hold if thats what version you are trying.
ahughes5 said:
I was finally able to get it working by flashing TWRP 2.8.0 via Odin 3.09 after flashing back to an old samsung base (pre-ANK1). I couldn't get TWRP 2.8.5 to hold if thats what version you are trying.
Click to expand...
Click to collapse
Yes, TWRP 2.8.5 is not working, I tried more than 5 times. I have ANK1 and TWRP 2.8.0. They work fine together.
Hi All - Same issue here. Same resolution.
For anyone needing an old stock base to flash to, I've mirrored AND4 here.
I downloaded it from Sammobile but their downloads are really slow, so just thought I'd put a mirror here in case it helps anyone.
I had the same issue and flashed back to AND4, but now I cannot root. It gets stuck on the cache.img and eventually fails.
Any ideas? Would like to be able to get TWRP on it.
---------- Post added at 10:25 PM ---------- Previous post was at 09:50 PM ----------
So I ended up doing a factory reset and all of a sudden TWRP 2.8.0.0 was working. Looks like I should be good to go.
Avalanche34 said:
I had the same issue and flashed back to AND4, but now I cannot root. It gets stuck on the cache.img and eventually fails.
Any ideas? Would like to be able to get TWRP on it.
---------- Post added at 10:25 PM ---------- Previous post was at 09:50 PM ----------
So I ended up doing a factory reset and all of a sudden TWRP 2.8.0.0 was working. Looks like I should be good to go.
Click to expand...
Click to collapse
for anyone with TWRP issues please head over to the TWRP Q&A thread we are working on a solution. From what i have heard TWRP for NK! build is broken right now.
http://forum.xda-developers.com/showthread.php?t=2922209
[Q&A] [TOOL/UTILITY][TWRP][2.8][RECOVERY] TWRP 2.8.0.0 TeamWin Recovery Project 9/16
Sent from my SM-T900 using XDA Free mobile app

[Q] 4G LTE issue

Hi guys. I got new N900T phone with stock rom. Latest updated was 4.4.2
Few days before Lollipo come up, I rooted my phone and when Lollipop 5.0 was published I installed 4.4.2 stock via Odin to update rom to 5.0 official. and I done that. All worked fine and as u all know, we couldnt write to SD card. My GPS worked fast, but I wanted SD card write. I rooted my phone to install SD fix, but I couldnt do that somehow (i got some errors) and I flashed official 5.0 Lollipop again via Odin. After that my GPS doesnt want to lock and I reset nv_build (something like that), now my GSP working but still I need 5-10 mins to lock. I have 4G issue now, even if I switch it to LTE, I dont get 4G LTE signal. When I put my SIM card to other 4G phone, 4G working, but on my phone doesnt want to work. ANy suggestion? solution? idea? to somehow reset 4G network, idk. 3G working. Ty
Samusng Galaxy Note 3 N900T
Lollipop 5.0 latest firmware stock official
Anyone?
Anyone?
Boot into twrp recovery, wipe data, system, internal storage, cache, dalvik cache. Pull battery for the 30 seconds. Insert battery. Enter download mode. Flash full stock 5.0 lollipop tar found on this thread. Maybe you already have the tar. Your phone should be good to go after that clean install.
http://forum.xda-developers.com/showthread.php?t=3047672
srod562 said:
Boot into twrp recovery, wipe data, system, internal storage, cache, dalvik cache. Pull battery for the 30 seconds. Insert battery. Enter download mode. Flash full stock 5.0 lollipop tar found on this thread. Maybe you already have the tar. Your phone should be good to go after that clean install.
http://forum.xda-developers.com/showthread.php?t=3047672
Click to expand...
Click to collapse
HI. Thank you on your time and help. I dont have twrp recowery. How to install it? Im on 5.0 lollipop stock.
srod562 said:
Boot into twrp recovery, wipe data, system, internal storage, cache, dalvik cache. Pull battery for the 30 seconds. Insert battery. Enter download mode. Flash full stock 5.0 lollipop tar found on this thread. Maybe you already have the tar. Your phone should be good to go after that clean install.
http://forum.xda-developers.com/showthread.php?t=3047672
Click to expand...
Click to collapse
It wont install TWRP recovery at all on my N900T Lollipop.
markokrstic said:
It wont install TWRP recovery at all on my N900T Lollipop.
Click to expand...
Click to collapse
Are you rooted? You have to root first using cf-auto root and then you install twrp recovery using odin. Do you need help on rooting phone or do you already know how to do that?
---------- Post added at 10:16 AM ---------- Previous post was at 10:10 AM ----------
I saw in your post that you have already rooted your device so after your stick rooted, boot into DL mode and flash this file in Odin on your pc and it will install twrp recovery. https://dl.twrp.me/hltetmo/twrp-2.8.6.0-hltetmo-4.4.img.tar.html
srod562 said:
Are you rooted? You have to root first using cf-auto root and then you install twrp recovery using odin. Do you need help on rooting phone or do you already know how to do that?
---------- Post added at 10:16 AM ---------- Previous post was at 10:10 AM ----------
I saw in your post that you have already rooted your device so after your stick rooted, boot into DL mode and flash this file in Odin on your pc and it will install twrp recovery. https://dl.twrp.me/hltetmo/twrp-2.8.6.0-hltetmo-4.4.img.tar.html
Click to expand...
Click to collapse
Hi. Thx again for your time. There was a issue with TWRP file from twrp website. I found another one here on XDA and worked great. I wiped all what u wrote in your post, installed again 5.0 stock via Odin and still 4G/LTE doesnt work.

SuperSU won't install through TWRP

Hello everyone,
I'm facing a very odd issue. I recently installed 7.1.2 from factory image and decided to also install TWRP in order to install a few modifications.
I was able to install the new kernel that allows Android pay to work with unlocked bootloader just fine.
However, I can't install SuperSU for some reason. I'm installing the zip file from TWRP just fine, however when I go searching for the app it's not there, and even if I install it from Google play it's telling me the system is not rooted.
I tried even downgrading a version of TWRP and SuperSU and still no go.
Anyone have any idea what is going on?
Thanks!
wireaudio said:
Hello everyone,
I'm facing a very odd issue. I recently installed 7.1.2 from factory image and decided to also install TWRP in order to install a few modifications.
I was able to install the new kernel that allows Android pay to work with unlocked bootloader just fine.
However, I can't install SuperSU for some reason. I'm installing the zip file from TWRP just fine, however when I go searching for the app it's not there, and even if I install it from Google play it's telling me the system is not rooted.
I tried even downgrading a version of TWRP and SuperSU and still no go.
Anyone have any idea what is going on?
Thanks!
Click to expand...
Click to collapse
Are you flashing su2.79sr3 ?
Make sure your using this one. Is the newest
Correct, I am flashing the newest and also tried previous version well, still no go!
wireaudio said:
Correct, I am flashing the newest and also tried previous version well, still no go!
Click to expand...
Click to collapse
Hello,
I'd try reflashing stock boot.img from your 7.1.2 factory image.
The fastboot boot TWRP.img and install TWRP zip.
Install SuperSU: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Reboot to system. From here you should have superSU​ installed.
Reboot to TWRP and install custom kernel zip.
Hopefully it will work...
Good luck...
I will try that, in that order, but before i do, can someone give me a brief explanation on what slot A and slot B are and what they do? I have a feeling it may have something to do with this. I looked for answers on the forums and I wasn't able to find a clear answer.
wireaudio said:
I will try that, in that order, but before i do, can someone give me a brief explanation on what slot A and slot B are and what they do? I have a feeling it may have something to do with this. I looked for answers on the forums and I wasn't able to find a clear answer.
Click to expand...
Click to collapse
Hello, it's right here: https://www.xda-developers.com/exclusive-dual-boot-may-be-possible-on-pixel-phones/
I also see you posting in another thread. I'm going to answer your question here, so all Infos remain in the same place...
wireaudio said:
I basically installed the factory image without the -w flag, turn booted in TWRP (without flashing TWRP) and installed kernel, then flashed super SU then rebooted. Didn't work so I rebooted in TWRP and flashed TWRP and then flashed SuperSU. Note that I had SuperSU installed in 7.1.1 so I assumed it would overwrite. It didn't work so I uninstalled old SuperSU and re-flashed SuperSU 2.79. it still didn't work so I downgraded SuperSU and TWRP one release and reinstalled. Still no go. And that's where I'm at.
---------- Post added at 09:18 AM ---------- Previous post was at 08:47 AM ----------
Better question is, how do we select what slot stuff gets installed in? It doesn't seem to be clear, more like a game of chance!
Click to expand...
Click to collapse
Your explanation in the other post and this one are different. Just try in the order from my previous post...
For your information, you can choose the active slot. It's not "like a game of chance". Just use the proper command:
fastboot --set-active=a
Or
fastboot --set-active=b
Good luck...

Can Android 10 beta be rooted?

If it can, how? I'm having bootloop issues trying to do that. Thank you.
Bootloop in logo S9
RpRAUC said:
Bootloop in logo S9
Click to expand...
Click to collapse
follow up
Piereligio said:
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
https://forum.xda-developers.com/ga...rooting-installing-twrp-t4012961/post81084623
The patched kernel contained here was the solution for me
S9 ROOT
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
viktorvlahov11 said:
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
Click to expand...
Click to collapse
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
it stucks for me on the samsung logo
aidenpearce296 said:
it stucks for me on the samsung logo
Click to expand...
Click to collapse
Try flashing the twrp flashable firmware it may fix your problem
---------- Post added at 08:41 AM ---------- Previous post was at 08:37 AM ----------
viktorvlahov11 said:
Try flashing the twrp flashable firmware it may fix your problem
Click to expand...
Click to collapse
Piereligio said:
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
Click to expand...
Click to collapse
I got it to work on a Bulgarian unlocked model
Maybe try flashing the twrp flashable firmware after the mod
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
viktorvlahov11 said:
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
Click to expand...
Click to collapse
I done that, but still stuck on SAMSUNG logo, no boot loop or what. I was waiting 10min, nothing happened.
Any advice?
Hi there,
after having tried different methods to root my S9, which has updated to Android 10 One UI 2.0 this morning, maybe the solution that finally worked for me will help you too.
First I tried to root just like in Pie, as found on the net: flashed TWRP 3.2.3 via Odin, then flashed Magisk with TWRP plus this no-verity-opt-encrypt. Got stuck in bootloop, tried different no-verity/dm-verity versions, Magisk 18.x and Magisk 20.1. Nothing worked, got stuck again every time i rebootet the system again.
Then, after realising that I CANT get back to Android 9 (old rom wasnt Odin flashable anymore, phone didnt boot, BSoD), I first downloaded the new stock rom and bootloader as zip, got it from here:
https://forum.xda-developers.com/showpost.php?p=81615561&postcount=1830.
You have to check if that fits with your version / phone. Once downloaded, I copied both onto my SD card. So now I was able to install at least the new clean stock rom. Oh, and now I used the TWRP version 3.3.1.
Then I found this:
https://forum.xda-developers.com/galaxy-s9/development/root-s9plus-exynos-android10-t4065343
At first I tried to root without the SoLdieR9312's mod, only with MAGISK 20.3 and no-verity. Stuck again, it only bootet to download mode, nothing else. So flashed again the clean stock rom, and after first not keeping the right order (I suppose) I finally followed EXACTLY the instructions 1 - 4 in above manual including SoLdieR9312's mod (I highly recommend first a complete Wipe, format data, and then flash the clean new Rom with Android 10 and bootloader from above link).
Now, to save you the time I spent today: once your phone is bootet (and succesfully rooted via Magisk 20.3, which will happen automatically due to the SoLdieR9312's mod), DONT LET MAGISK UPDATE TO VERSION 20.4!!!! Magisk Manager asks you to update, but when I did update to 20.4, everything fell apart again, it only bootet to download mode.
Now I seem to have it stable and running with 20.3 and the [email protected]. I rebootet 5 times so far just for the sake of it, and it works fine and rootet.
If I can be of further help, please let me know. I spent the last 12 hours on this matter, so dont hesitate.
Greetz from me minus a bunch of nerves
PS: After I wrote the above, I deleted the Knox family in the rootet system, and then it collapsed again and, after BSoD, it only rebootet into download mode. I can not exclude the possibility, that this might have been the reason for some system breakdowns before, as I had to re-do the wipe-clean-install-then-root-then-customize worksteps aroung 8 times yesterday before it was stable as it is now. Now I´ll leave Knox on it, though that itches me a bit. But I´m exhausted for now
PPS: IMPORTANT when I try to create a PIN or a pattern for the lock screen, phone reboots to SIM card PIN screen and then keeps rebooting and rebooting. It looks like there are some interferences with root and PIN / security. I did NOT create a Samsung account, only a google one, cause in the beginning i suspected it might have been a Sam acct problem (I constantly couldnt log into it on the phone). Turns out that might not have been the case, rather a prob between root and setting a lock screen security.

Categories

Resources