Specs:
T-Mobile-locked Samsung Galaxy Note 8 - N950U
Baseband version: N950USQU1AQI5
Build number: NMF26X.N950USQU1AQI5
Android version: 7.1.1
Samsung Experience version: 8.5
Knox version: 2.9
I recently purchased the above Note8. I have bookmarked a root method[1], but it requires bootloader v7. If I'm decoding my phone's baseband version correctly, its on v1, so probably won't work with this method.
I'm wondering, if I let it do an OTA update to Oreo (Android v8), will it hit the requisite v7 bootloader so I can, according to the instructions on that page, flash it back to a pre-rooted Nougat? ( If there's a better method than what I'm planning to follow, please advise. I'm all ears! )
[1] www (dot) the custom droid (dot) com/root-galaxy-note-8-snapdragon-n950u/
Just stay on firmware you are on and use the old Samfail root method
Sent from my SM-N960U using Tapatalk
Thanks, butchieboy. Would this be the process for this phone?
https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340
Yes [emoji106] The thread is closed but you should still be able to get the files you need. If not I still have them and when I find time I could send them to you with Mega...but you still should be able to get them from the thread.
Sent from my SM-N975U using Tapatalk
The links are still good in that post, but I'm a bit concerned about them. The SamFAIL downloads for the v1 bootloader are designated for N950F ("for the Samsung Galaxy Note 8(SM-N950F)"), which is the European firmware. Mine's N950U (US).
Does this SamFAIL root actually rely on the European firmware? How does that impact the Snapdragon? I thought the European phones/firmwares were designed for a different processor.
No dice
I followed the instructions on that post to the letter. The first flash didn't cause my phone to reboot (as the instructions say it will), so I rebooted it myself and got it back to the "Emergency" screen, whereupon I did the part #2 flash. It reset that time, and now it's stuck in an "Installing update" loop with the Android icon (with a "warning" icon above it) just appearing over and over.
What do I do now? Do I have to try and flash a stock ROM and see if I can recover the phone? Or is there something I can do from here that will help it continue?
Boot to recovery and factory reset
Sent from my SM-N975U using Tapatalk
And the angels sang!
Since I couldn't get the damn thing to shut off anyway, I left the phone in the "Installing" loop overnight (since that was the least risk of screen burn). This morning, the device was dead because the battery had drained to zero, so I put it on the charger. I left it there for only about 30 minutes so it had just enough juice for me to try and get it into recovery mode.
I must not have held the buttons correctly, because it went into a normal boot instead of going into Download or Recovery. I let it go, intending to just try again once it entered the "Installing" loop, and LO! the "SAMSUNG" logo came up. It hadn't done that before. I put the phone aside and didn't touch anything while the logo pulsated, and it eventaully dropped into the setup screen! :victory: Of course, it almost immediately shut down because the battery hadn't charged enough, but I think it somehow reset/corrected itself when it lost all power overnight.
I left it on the charger and monitored the level. It stopped increasing at 80%, which is the expected behavior with this solution. I powered it on again, and everything is as described in the rooting post (except that SuperSU did not prompt me multiple times to update it).
So, at this point, I'd say I'm good. Looks like it reset itself, and the root succeeded. Hopefully anybody coming along later with this same issue on the Note 8 will see this post.
Thanks again, butchieboy.
Related
Hi guys I'm trying to flash Jovi's Custom Rom. I accidentally pressed the update button on my phone that allows the Latest update from t-moble to kill the phone so It wont charge. Luckily I have quite a but of battery power left and I'm franticly trying to flash a jovi's custom rom. currently I'm getting a "Failed" message when trying to flash on ODEN 3.12 here are the directions I followed to the letter but no success.
First Thing Your Going To Do Is Download Both graceqltetmo_N930TUVU1APGC_Stock_Deodexed.zip And N930T_Note7_Adb_Rootkit_And_Odin_Pack.zip Files From The Download Link Section Below.
2. Extract All The Files From N930T_Note7_Adb_Rootkit_And_Odin_Pack.zip Onto Your PC Desktop, You Will Then Have Eight Files On Your Desktop Which Will Be MODIFIED_TMO_SPR_N930PVPU1APH3_REV00_ENGBOOT_FIRMW ARE.tar.md5, graceqltetmo_N930TUVU1APGC_Stock_Deodexed.img, SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe , adb-setup-1.4.3.exe, CommandPrompt.bat, Odin3.exe, Odin3.ini, And sun7.
3. If You Haven't Setup ADB On Your PC Yet Or Installed The Samsung USB Drivers, Just Open Both Executables SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe And adb-setup-1.4.3.exe And Complete Both The Setup Processes. Once Done You Should Now Have A Created ADB Directory Which Should Be Located At C:\adb. Once ADB Is Setup, Place The sun7 Folder And CommandPrompt.bat Inside Your ADB Folder From The New Directory.
4. Now Put Your Phone Into Download Mode By Powering Off Your Device First And Then Hold The "Volume Down+Home+Power Buttons" At The Same Time Until You See The Download Mode Warning Screen. Now Press The "Volume Up Button" And Then Insert Your Samsung USB Plug.
5. Now Open Odin3.exe, Click On "AP", Select "MODIFIED_TMO_SPR_N930PVPU1APH3_REV00_ENGBOOT_ FIRM WARE.tar.md5", And Then Click On "Start". Wait For A Couple Of Minutes For The Modified N930PVPU1APH3 Engboot Firmware To Finish Installing. After this step it says failed so this is where I'm suck currently at the bootloader. thanks guys for your help
Does your phone still work?
Proud owner of the Samsung Galaxy Note 7. ? Take that Samsung ???.
shanda5303 said:
Does your phone still work?
Proud owner of the Samsung Galaxy Note 7. Take that Samsung .
Click to expand...
Click to collapse
It still works its just stuck at the boot loader. I think when I attempted to flash the stock rom back on the phone It wiped everything. Honestly I'm not trying to root I'm just trying to install the stock rom
You should be able to download it in Sammobile, they usually have every firmware available for Samsung phones. Then you would want to checkout the N7A their accepting beta testers for v2 of the app. Maybe check with them before to see how you should proceed on reinstalling the initial firmware to avoid the update again.
Proud owner of the Samsung Galaxy Note 7. ? Take that Samsung ???.
shanda5303 said:
You should be able to download it in Sammobile, they usually have every firmware available for Samsung phones. Then you would want to checkout the N7A their accepting beta testers for v2 of the app. Maybe check with them before to see how you should proceed on reinstalling the initial firmware to avoid the update again.
Proud owner of the Samsung Galaxy Note 7. Take that Samsung .
Click to expand...
Click to collapse
Ok thanks. I'm doing that now Ill keep you posted of how it goes. thanks for the help I appreciate it.
[email protected] said:
Ok thanks. I'm doing that now Ill keep you posted of how it goes. thanks for the help I appreciate it.
Click to expand...
Click to collapse
No problem I've been using package disabler pro & N7A's shield for a while now and haven't had any issues. Plus N7A is a really great community especially when other forums don't provide much assistance. I think about 80% off the people still using the Note 7 have either joined N7A or the N7 Rebels (I've heard they charge for their app & assistance but haven't verified myself). ?
Proud owner of the Samsung Galaxy Note 7. ? Take that Samsung ???.
shanda5303 said:
No problem I've been using package disabler pro & N7A's shield for a while now and haven't had any issues. Plus N7A is a really great community especially when other forums don't provide much assistance. I think about 80% off the people still using the Note 7 have either joined N7A or the N7 Rebels (I've heard they charge for their app & assistance but haven't verified myself).
Proud owner of the Samsung Galaxy Note 7. Take that Samsung .
Click to expand...
Click to collapse
Ok cool I just signed in to N7A site. It looks really informative. I downloaded the firmware from sam mobile as you suggested also I have about 10 more minuits before its done downloading. ill keep you posted.
Ok I'd check the help and tutorials section for re-flashing firmware after an update, cause I'm not sure how you would avoid getting the update again unless you have a some sort of shield or package disabling app in place.
Proud owner of the Samsung Galaxy Note 7. ? Take that Samsung ???.
downloading the shield now. hopefully this works because I had to go back to using my note 3. and I'm like OMG what a major downgrade
[email protected] said:
downloading the shield now. hopefully this works because I had to go back to using my note 3. and I'm like OMG what a major downgrade
Click to expand...
Click to collapse
I have a Note 5 as a backup and even that feels like a major downgrade I can't imagine what a Note 3 would be like.
Proud owner of the Samsung Galaxy Note 7. ? Take that Samsung ???.
shanda5303 said:
I have a Note 5 as a backup and even that feels like a major downgrade I can't imagine what a Note 3 would be like.
Proud owner of the Samsung Galaxy Note 7. Take that Samsung .
Click to expand...
Click to collapse
Hey just giving you an update. Phone still stuck at boot loader but I have watched the lady known as catwoman video on youtube. I have downloaded and unzipped all the files and even tried to flash without success. Oden keeps giving me a fail. The only problem is with the smart switch application she recommended for download. I downloaded it and ran the app like suggested. It said that the my device is unsupported by smart switch. I cam to the conclusion that this is the way I should have started vs wiping everything which is the reason I'm stuck at the boot loader because there is no data on my phone. Here are the steps I took to get past this problem.
1. Reinstalled Smart Switch, but after the re- install no success.
2. I reopened Smart Switch and clicked the tab that says "MORE" then on Emergency Software & instillation. I followed the steps which included imputing my device model number and S/N. Did that but my device is still reading as a unsupported device on smart switch. I'm in progress of contacting her to see if she or any of her team as any ideas. Hopefully I'm back up and running soon. I cant wait for the note 8 so I can be done with this
Hey just giving you an update. Phone still stuck at boot loader but I have watched the lady known as catwoman video on youtube. I have downloaded and unzipped all the files and even tried to flash without success. Oden keeps giving me a fail. The only problem is with the smart switch application she recommended for download. I downloaded it and ran the app like suggested. It said that the my device is unsupported by smart switch. I cam to the conclusion that this is the way I should have started vs wiping everything which is the reason I'm stuck at the boot loader because there is no data on my phone. Here are the steps I took to get past this problem.
1. Reinstalled Smart Switch, but after the re- install no success.
2. I reopened Smart Switch and clicked the tab that says "MORE" then on Emergency Software & instillation. I followed the steps which included imputing my device model number and S/N. Did that but my device is still reading as a unsupported device on smart switch. I'm in progress of contacting her to see if she or any of her team as any ideas. Hopefully I'm back up and running soon. I cant wait for the note 8 so I can be done with this
Can someone please help. I'm getting desperate now. I flashed a Nougat build a little while ago but had some issues with Bluetooth and NFC so I flashed back to the original firmware using the dload folder and 3 button method. The installation seemed to go through fine but get's stuck booting at the vodafone logo. It then takes me into eRecovery where it attempts to download latest version over wifi but fails. I don't really know where to go from here because I can't access the internal sd card because the phone won't boot. I can access fastboot but don't really know what to do from there.
stevemacer10 said:
Can someone please help. I'm getting desperate now. I flashed a Nougat build a little while ago but had some issues with Bluetooth and NFC so I flashed back to the original firmware using the dload folder and 3 button method. The installation seemed to go through fine but get's stuck booting at the vodafone logo. It then takes me into eRecovery where it attempts to download latest version over wifi but fails. I don't really know where to go from here because I can't access the internal sd card because the phone won't boot. I can access fastboot but don't really know what to do from there.
Click to expand...
Click to collapse
Stevemacer10 Hello, I hope to be keen to help, because it happened to me the same thing, with two days of stomach ache for it. In wanting to load Android on my Nougat Huawei P9 Plus VIE-C02, with VIE-L09C605B354 and VIE-L29C185B320 I went into semi-brick or brick, or was only in bootloader, the screen with the green man to speak. No avail various ways, including via microSD-Fastboot or ADB to do restart your phone. Then, to my previous experience with a Huawei tablet, I logged on to the 'https://www.dc-unlocker.com/' site, and essend already registered, I bought 15 credits (15 Euros), for the 'option' DC Phoenix Firmware write ', valid for 72 hours, in addition to the program and downloaded the' DC program Phonix v29 '(https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial) following the related tutorial. Obviously procured the original firmware 'VIE-L09C02B133' or even lower versions, you'll have to unpack in a folder of your preference. Unfortunately, despite having used with DC Phoenix the original firmware was always also blocked me. At that point I wanted groped with a firmware that you can find on the same site of the DC-Unlocker (https://files.dc-unlocker.com/user.html?v=files/57694006a60d7) by downloading the firmware 'VIE_AL10B_M00A063_Factory_firmware_China_Nonspecific_Android_6.0_EMUI_4.1 .dgtks', which I loaded with DC-Phoenix on the phone. Rebooting of a minimal mode of andorid, I did not see well either. I went back into bootloader, as well as devone be made the previous steps that I have already described to you, and this time with DC-Phoenix I loaded on the phone firmware L09C02B128 and everything went well. Attention and keep in mind that just as I happened to me, the serial number of your phone is changed, to me has happened in '0123456789ABCDEF' and there was no way to change it, so as, while having the unlocked bootloader can not longer charge the TWRP recovery in order to then have root permissions. Until reading the paragraph '(Optional) Phone numbers REPAIR', I went to that point on the site 'http://hcu-client.com/'. Also here are sadly bought 8 credits (8,00 Euro) in order to work with the program 'HCU-Client v1.0.0.0115', you need to download and unpack, then follow the various instructions, which are not difficult when you have to be walked through the modding, otherwise you do even more damage. Let me know what you did and how it went to the method. I hope also good for you. In summary we want Euro 15 for Phoenix whose duration of operations applies to 72 hours and 8 Euro per HCU-Client, it can only use this for 24 hours.
P.S .: Obviously if you follow my instructions and all these signs you do so at your own risk, esonerandomi from every possible and accidental deterioration of the situation and the damage to your phone. Sorry for my English, whose translation has made Google translator.
---------- Post added at 12:59 AM ---------- Previous post was at 12:33 AM ----------
I wanted to say that the change of the serial number does not work well. The serial number has been changed from what I've shown you above, but was not put one I added that I had from the sales box. I write support and maybe let you know what they tell me. See you soon.
Hi Grlshia,
Thanks for getting back to me. It's such a minefield playing with all these different regional variants. I have though, managed to get it completely fixed. I just gave in and took it into the local Vodafone store and fortunately there happened to be one of the tech experts in there that owned a P9. He took it off me and within about 5 minutes he had completely restored it. He told me he just did a factory reset by holding down vol+ and power. I'm sure I had tried this myself to no avail previously but that's what he said he did.
stevemacer10 said:
Hi Grlshia,
Thanks for getting back to me. It's such a minefield playing with all these different regional variants. I have though, managed to get it completely fixed. I just gave in and took it into the local Vodafone store and fortunately there happened to be one of the tech experts in there that owned a P9. He took it off me and within about 5 minutes he had completely restored it. He told me he just did a factory reset by holding down vol+ and power. I'm sure I had tried this myself to no avail previously but that's what he said he did.
Click to expand...
Click to collapse
Stevemacer10 hello, I'm glad you've solved the problem. Unfortunately I'm still fighting because, for now I can only and even to load its firmware, but if you want to try to load the TWRP recovery for later obtain root permissions, it always fails. From what seems to understand me and certainly due to the fact that the bootloader unlock code now is different from what I have, because as I told you the serial number has changed and if I request a new unlock code, it stops notiziandomi the procedure that there is inconsistency between this number and the IMEI. For now I do not know what to do and how to proceed. I hope that over time can still solve my problem. A good evening to you :good:
i'v been throw it
after updating my p9 plus with a firmware that is not sutable to my area
my phone restarted and ask for an account wich ok but the problem was that the software not working properly and missing a keyboard.
and will not go to recovery mode to try another software.
this sloved by downloading a sutable correct software and unzip it into an SD card folder (i create) called dload, then swich off the device and turn it back on while holding three bottons (power+v up+v down) 10 to 15 sec. and the phone directly read from the SD card and start updating a new firmwarw.
try it.
it success with me , hope it work wth u
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
tolerant said:
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
Click to expand...
Click to collapse
dmccort said:
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
Click to expand...
Click to collapse
Good luck, i did read that it might be possible to install the base firmware back to it and then update again.
Im sure we are not the only people this has happened to and if you succesfully do this, maybe consider making a full step by step guide so to help others.
Fingers crossed
:good:
Will do my best.. So far it's been a major. I've managed to flash a working stock ROM and boot up. But there are a few things to smooth out. Such as, I have no IMEI number now and the build is C900, also the bootloader is modified.
To get it to boot I had to use DC- Phoenix to flash a factory firmware(Chinese) which I had to pay for. Then I flashed a stock vie-l09c432b181 ROM over the top.
To repair the IMEI I'll have to use HCU, which I'll have to pay for as well. But that's ok. If I can get my original IMEI back, I can use the original unlock code I got earlier this year, otherwise I'll have to get a new one based on a new IMEI.
I can repair the bootloader and region code using twrp etc. so that's not a problem.
I'm actually using the phone to write his reply, so I can at least use it.
Once I have it all 100% working I'll try to put together a full step by step.
Cheers.
Well, I have a working phone. But, it'snot stable. Having trouble with mobile connection, sms, mms, 4g etc not staying connected. So wont be doing any write-ups just yet.
Not until it's stable.
I'm wanting to return it to complete stock now. And that requires trying to find an oeminfo file for C706 (New Zealand).
Will add more as I get there. Sorry.
I had the same problems. All I did is updated the phone with the firmware you want via Twrp . Be warned that it will replace the recovery back to stock. Also clear the cache and etc.
I had a similar issue with SRK tool, bootlooping, won't flash new firmwares, lost all the stock apps and diagnostic tools.
I'm now stuck on a TEST-KEYS build with no NFC or Bluetooth.
My solution was to throw the piece of junk in a drawer, forget about it and I went and bought a Pixel XL instead - a phone that is properly supported and gets updates quickly.
After much messing and a headache I finally got to c432b370
And everything back to normal
tolerant said:
After much messing and a headache I finally got to c432b370
And everything back to normal
Click to expand...
Click to collapse
How did you succeed?
I am stuck on TEST-KEYS but I am not able to flash other roms on it. When I go to recovery, the update process stops after a while
Sent from my VIE-L09 using Tapatalk
Most of the time I am the guy helping people out. This time I think I did something pretty dumb.
I have an old "beater" P9 plus that I was using as a casual gaming device. Most of the apps I was using were beginning to no longer be supported because for some reason the device NEVER updated. Any time I check for a possible update the phone stated it was up to date. After much searching I discovered that this device SHOULD have updated quite a few times.
I used firmware finder to find a supported update and the first one went somewhat unexpected. The firmware was downloaded and put in the correct folders but kept failing after 5%. I decided that the next thing to do was to find a cool rom and go through the process of unlocking and installing TWRP. I usually try to install the latest TWRP. This turned out not working at all so I went for an older version and it booted into TWRP, however it found the update and installed it!
I kind of wanted to keep it stock, but updated stock so I went for a bigger upgrade to Android 7 firmware. This only worked partially and (stupid and I know better) forgot to do a backup. I did not know that TWRP was gone and root was gone. The battery died and I rebooted like normal and there was a much improved interface. However, a good bit of stuff stopped working like bluetooth and the boot screen was in red stating the device can't be verified and ended up in something like a NOR905 test keys build. I did a backup, selected a downgrade package that was checked and "updated" to the downgraded firmware through Project Menu. It successfully stated it was 100% complete.
Now it is stuck on the boot screen for an unlocked device.
What works (or is possibly a good thing):
The hardware keys can get me to the bootloader (fastboot)
ADB recognizes the device is in fastboot
Phone is Unlocked
FRP is unlock
What doesn't work:
Everything else. All I have is fastboot and an unlocked bootloader. I can try to flash recovery but that never boots, it just stays suck on the recovery boot screen. The system will not boot at all.
UPDATE:
I broke down and spent the money to use the DC-Phoenix software to unbrick the phone. Several of the options for firmware did NOT work. The one file set that did work was to use this firmware:
VIE-L29_C900B101_Firmware_countryValue_Nonspecific_Android_6.0_EMUI4.1
Then use this as the customization:
update_data_C900B101_hw_default
The phone originally started out as VIE-L29C636B130. This changed it to VIE-L29C900B101 and is on EMUI 4.1 android version 6.
Now the fun part is going to see if I can find a version of TWRP that will work and see if I can root it. Maybe even try a custom ROM. We'll see though. The device is just an old beater for fun. But at least, she's not broken anymore. Guess I'll grab a beer and celebrate my "unbricked" device.
I was happily use my Note 9 N960N(Korean set) after I rooted it about a year ago. Few days ago I saw a new ver of Magisk(old ver 17.2 flashed w/TWRP) at Magisk manager and wanted to update but hesitate. I backup a few important file like whatsapp, SMS & contact list before I carry on further. Today I decided to update the Magisk and my fear was right, after it reboot my Note 9 stuck at "Samsung" logo. I let it there initially and after a while it remains at same place. I tried to switch it off by press the power button but no response. It won't switch off after I tried, 10, 20 and 30 seconds. I found out there is a way to reboot it by holding "power + volume down". I successfully got it boot to recovery to TWRP.
I thought it maybe the Magisk was corruptted during update so I download the Magisk zip v19.3. Then I booted to TWRP and installed the Magisk zip. I reboot the Note 9 after Magisk installed. Again I was stuck at Samsung logo. I thought maybe the sequence was not correct; beside the Magisk there maybe need few more so I followed the root sequence(skip root); 1. Magisk 2. no-verity-opt-encrypt-6.0 3. RMM-State_Bypass_Mesa_v2
Same problem, I stuck at Samsung logo. As early problem, I couldn't switch it off by pressed the power switch. I have to reboot to TWRP and use its interface to power off the phone. I have new problem this time; once I pressed the power button to power on the phone, it will goes to TWRP straight away. Tried few times and it remain the same problem. The last action what i did is flashed a new TWRP v3.3.1-0-crownlte and it didn't help either.
My Note 9 has 2 problems;
1. go to TWRP recovery straight after press power button to power up the phone.
2. stuck at samsung logo after user TWRP to reboot.
There is one more thing I didn't pay attention previously, the "mount" in the TWRP what is supposed to mount? It "mount" the SD card when it last to flash zip files.
Appreciated anyone can helps, thanks.
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
user109 said:
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
Click to expand...
Click to collapse
Phone will factory reset after flash stock regardless odin or smartswitch. Of course you can still flash oreo. But flashing stock should be the last resort.
Rosli59564 said:
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
Click to expand...
Click to collapse
You did mention to flash a different kernel, what will it be the most suitable?
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
user109 said:
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
Click to expand...
Click to collapse
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
N1NJATH3ORY said:
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
Click to expand...
Click to collapse
Hi N1NJATH3ORY, I did google around the screenlock loop problems and most of them done with 1) simple reboot 2) boot to safe mode 3) use "samsung "findmymobile". A most common solution; "wipe". A few issues raised at Samsung forum but not helpful; "call Samsung support".. There was an interesting article which suggested the problem is from google itself. Here is the link; https://www.androidpolice.com/2019/12/12/google-pixel-pin-lock-screen-loop-help/
"If the encryption of the "Synthetic Password Key blob", which needs to be decrypted in order for the unlock process to be resolved, is not able to retrieve a stored decryption key if it was corrupted." from the article. I'm not sure if this is the cause but from logic point of view it's possible. I believe the bloody Samsung knew this problem since day one but because it's not a"common" issue Samsung just swipe under the carpet.
What I did on my note 9 last action was reflash the oreo, if in the process of flashing the "Synthetic Password Key blob" has been wiped out then it may explain this screenlock loop problem, which I hope not to happen. I'll be screwed if it did. :crying:
I'll wait its battery to drain out to see what happen even though I doubt if any change..
As expected, the drained out of battery did not help, my note 9 remains locked. The only way is to try out new method and with high risk which will wipe out my data. Fortunately the new method work! Not only it overwrite the lock screen loop and also disable the google device lock.(One of the method I tried during my lockscreen loop which is useless. It creates an extra problem on top of the problem) I got all my data intact and allow me to do all backup. :highfive:
summary: update Magisk is not a full proof. The risk is 50% it will brick the phone. My advise is to backup every dan internal data before finger press the Magisk "update" especially it remaps the image! Manager APK is okay to update. I learned from the hard way and almost lost the whole dan data in my Note. You have been warned!
Gdhhs