Hello All:
I have been using and tinkering with phones for years now, note 2,3,4 and 5. I say this so you understand I'm not new to fixing usual issues with rooting and flashing custom roms, etc. There may be a solution to this, but I haven't been able to find it after weeks of searching and trying different things.
After flashing Tek's Rom with COJ -> COK my phone gets the "This phone has been flashed with unauthorized software and has been locked..." error no matter what I do. I have completely wiped, formatted, Odin'd stock firmware and flashed and flashed every bit of software I can find, including using at least ten fresh md5 verified new downloads of the firmware, etc. I have tried arter97's kernels including last several versions, and several other kernels I can't remember.
Anyway, when I complete wipe and format, and then Odin flash the stock firmware (COK), my phone never leaves the Samsung Note 5 boot screen. If I flash a kernel, I can get to the setup mode, but I get the error message that my device has been locked and cannot make calls or register my phone on the tmobile network. My sim card works just fine with other phones. I am using it as we speak on a Lumia 950, but I cannot stand not having the spen.
I have tried flashing kernels through philz, twrp, and the stock recovery. I have tried OTG and flashing kernels from the internal SD card once I flash a kernel and get past the setup. Since I use two step verification, and cannot receive texts, it's a real pain to get into my google account.
When I try to login to my Samsung account, it says, "processing failed," each time. Tmobile has been less than helpful. I am at wit's end. Anyone have any thoughts? I'd really appreciate the help.
Thanks.
Make sure you have everything backed up. Odin to stock be sure OEM unlocking is on. Do a full wipe in stock recovery. then try to root again.
steve97ta said:
Make sure you have everything backed up. Odin to stock be sure OEM unlocking is on. Do a full wipe in stock recovery. then try to root again.
Click to expand...
Click to collapse
Forgive me, and thank you for your reply, but I am not sure if I could have been any more clear that I have full wiped, odin'd back to the stock firmware, etc. no less than a hundred times. Not only that, but I have tried COJ, COK, all three recoveries, different kernels, etc. I can assure you OEM unlocking is on, and has been on each and every time.
In ODIN Mode (Download Mode), my phone reads:
Download Speed: Fast
Product Name: SM-N920T
Current Binary: Samsung Official
System Status: Custom
FRP LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0301)
RP SWREV: B:2 K:0 S: 0
It does not change much when I flash a kernel or a custom rom, other than current binary to "Custom"
Anyway, I want to be clear:
I have turned on OEM unlocking, no fingerprint lock or any lock mechanism, full wiped through philz recovery, twrp, etc. and ODIN flashed the STOCK firmware from this forum, from Tek's thread, from Sammobile (I even paid the $10.00 to make sure), and I absolutely cannot get my Sim card to register on the network.
I tried again this morning. First, I full wiped and ODIN'd COJ. Then, I full wiped and ODIN'd COJ w/NAND Erase All. I should note that each time I boot to recovery, I get the same old message, "DM-Verity Verification Failed... Need to check DRK first..."
I also get this error when I wipe, "preload checkin... E: failed to mount /preload (no such file or directory)"
I then full wiped and ODIN'd COK. I rinsed and repeated. I still get the exact same errors I mentioned above. The phone sits still at the Samsung boot screen (it does not get to the colored logo screen or the T-Mobile screen, just the black and white) for as long as I will allow it (sometimes hours).
Update:
I have now individually full wiped and flashed the BL, AP, CP, CSC, and PIT files multiple times with no changes. I have read somewhere that I may need to unpack the firmware file itself and remove the cache.img file?
If you are using odin you should only need to put the tar in the AP slot. Are you using the factory note 5 cable? Also what version of odin?
steve97ta said:
If you are using odin you should only need to put the tar in the AP slot. Are you using the factory note 5 cable? Also what version of odin?
Click to expand...
Click to collapse
Yes. I am trying additional methods because, as I have said, I have already tried to do the basic methods of wipe data / internal storage / system / cache /dalvik cache (10x), ODIN stock firmware, rinse repeat.
Yes, I am using the factory cable.
Odin version 3.10.7
I am however having additional issues caused by my efforts. My E:/data partition seems to be missing.
Thanks
er0k02 said:
Yes. I am trying additional methods because, as I have said, I have already tried to do the basic methods of wipe data / internal storage / system / cache /dalvik cache (10x), ODIN stock firmware, rinse repeat.
Yes, I am using the factory cable.
Odin version 3.10.7
I am however having additional issues caused by my efforts. My E:/data partition seems to be missing.
Thanks
Click to expand...
Click to collapse
That happened to me if you have a backup of your efs partition you can restore and it should fix verify your imei that is the same as the one it has on the box on a sticker @Jammol can help in here he is the one that helped me he is good at this kind of stuff and remember to always do a backup i learned from this thing too
This only means your imei is messed up same things that you mention happened to me even that samsung account failed stuff and all it was the imei lol
Sent from my SM-N920T using Tapatalk
Ok, thanks. What happens if I do not have an EFS backup? I may have a NANDROID from TWRP somewhere, but I doubt it.
I know you did a million things.
For me, after I flash stock unrooted thru Odin, I will get bootloop until I wipe in Stock recovery.
I appreciate that, but yes I had also tried that. At this point I think the poster above is correct in that I need to restore the EFS partition. I have read tricks of switching the mount point, and also about using some "magic" tools online. Does anyone know how I can fix the missing partition? Tmobile isn't helpful, and I can't get on the phone with anyone from Samsung.
Also, update: I was able to successfully flash the android 6.0 rom on cokc firmware last night, but it is still giving me the same problems not recognizing my sim and not working as far as registering on the network. I also cannot login to my Samsung account.
I really appreciate the help.
er0k02 said:
I appreciate that, but yes I had also tried that. At this point I think the poster above is correct in that I need to restore the EFS partition. I have read tricks of switching the mount point, and also about using some "magic" tools online. Does anyone know how I can fix the missing partition? Tmobile isn't helpful, and I can't get on the phone with anyone from Samsung.
Also, update: I was able to successfully flash the android 6.0 rom on cokc firmware last night, but it is still giving me the same problems not recognizing my sim and not working as far as registering on the network. I also cannot login to my Samsung account.
I really appreciate the help.
Click to expand...
Click to collapse
Just as cautionary reminder, always make sure that OEM Unlock is turned on before flashing anything whatsoever. Even if you're on a custom rom already. I flash almost daily and I check every single time before I flash something. YOU NEVER KNOW!
You said earlier up that you have a TWRP right? If you still do check it to see if it has a backup of the EFS partition. If you do have the EFS partition backed up, try and remember what firmware you were on. You'll need to be on that firmware when you restore it. In other words, if you were on COKC when you made it, you'll have to be on that when you restore it. Also try restoring it on TekHD rom if you were on COKC when you made the backup. Don't wipe anything, and reboot after the restore. ONLY RESTORE THE EFS, NOTHING ELSE!!! Upon reboot, if you have a fully working phone again, do a factory reset from inside the rom. Once it reboots, if it works still, download his Stock Rooted Rom in post 5. Do a full wipe and flash that, your EFS should not wipe. Once rom is done flashing, reboot and see if you still have a fully working device. If you do, go ahead and try an Odin flash to full stock. Do a full wipe before using Odin.
Jammol said:
Just as cautionary reminder, always make sure that OEM Unlock is turned on before flashing anything whatsoever. Even if you're on a custom rom already. I flash almost daily and I check every single time before I flash something. YOU NEVER KNOW!
You said earlier up that you have a TWRP right? If you still do check it to see if it has a backup of the EFS partition. If you do have the EFS partition backed up, try and remember what firmware you were on. You'll need to be on that firmware when you restore it. In other words, if you were on COKC when you made it, you'll have to be on that when you restore it. Also try restoring it on TekHD rom if you were on COKC when you made the backup. Don't wipe anything, and reboot after the restore. ONLY RESTORE THE EFS, NOTHING ELSE!!! Upon reboot, if you have a fully working phone again, do a factory reset from inside the rom. Once it reboots, if it works still, download his Stock Rooted Rom in post 5. Do a full wipe and flash that, your EFS should not wipe. Once rom is done flashing, reboot and see if you still have a fully working device. If you do, go ahead and try an Odin flash to full stock. Do a full wipe before using Odin.
If you need further help, add me to Google Hangouts [email protected]mail.com
Click to expand...
Click to collapse
Thanks, I'll add you to hangouts. I don't have a backup EFS, for sure.
Possible to fix a corrupt EFS partition without a backup?
Man, I am in the same boat. I do not have an EFS backup. Any help would be appreciated.
I've done it. I am no longer locked out of the network, no longer getting the error, EFS fixed without a backup, Samsung account accessed.
I'll write out the steps and post in a bit. Battery is dying.
Thanks
Do you have the steps to recover the EFS? I've been stuck for few days now and feel it is a crime to exhaust every option as you already figured it out. Thanks for the share either way!
just throwing in my two cents...I have this same bizarre boot loop, Odin not sticking crap. the fact it still says your system is custom tells me it's in the same ball park.
do everything you usually do, then reset twrp settings to default, reboot to recovery, wipe all cache blah blah, then reformat to ext4, repair, resize every partition. to get davlik, select it and system together, then file system to ext4, to get the internal storage, select it with data. then reboot recovery...MOUNT SYSTEM...do it all again...
reboot, let it get stuck at logo...reboot to recovery clear caches, MOUNT SYSTEM, DO IT AGAIN.. just the caches...
you're welcome
you're
er0k02 said:
I've done it. I am no longer locked out of the network, no longer getting the error, EFS fixed without a backup, Samsung account accessed.
I'll write out the steps and post in a bit. Battery is dying.
Thanks
Click to expand...
Click to collapse
It would be interesting to know how you solved this. I just made sure I have an efs backup.
I completely forgot about this thread. I apologize to everyone for the delay.
To recap:
My phone was cellular bricked. It turns out I had a corrupted EFS partition. The way I managed to "fix" the problem was tedious and may not work for everyone.
1. I ODIN flashed the stock firmware multiple times;
2. I erased the data in my Samsung account. I had to do this online through their website. I think this was crucial.
3. During each initial ODIN flash, I selected Phone EFS clear, Phone Bootloader Update, Nand Erase All, Repartition, etc. in ODIN.
4. I then re-flashed stock COJ without selecting EFS clear, Phone Bootloader Update, Nand Erase All, Repartition, etc. I just let it select the normal options.
5. I then ODIN flashed TWRP, and flashed Jovy's ROM after flashing the Stock Modified Kernel.
6. I used the tool inside Jovy's Aroma installer [Fix Corrupt EFS Partition, or whatever it is called];
7. I didn't install any of the Samsung apps.
8. I then installed the ROM.
9. As soon as the ROM booted, I connected to WiFi as quickly as possible and ran through the steps as fast as I could before I gave T-Mobile the chance to display the message that my phone had been rooted and would no longer be able to connect to the cellular network. I logged into my google account and rebooted quickly before anything else happened. This took less than 30 seconds.
10. I went back into TWRP, full wiped and formatted.
11. Back to ODIN flashing Stock COJ.
12. ODIN flash TWRP.
13. Flash Jovy's ROM + Stock Modified Kernel.
14. Restore EFS partition.
15. Install ROM.
16. Finished.
It has been working since the day I posted above.
Try this tool
You might want to verify if Smart Switch tool by Samsung works on your device. I had a problem flashing my note 5 with the oem lock and this program saved the day. Is free and you can google it, I hope it helps.
Sorry, thanks, but no, if you choose to read this thread, you will understand that Samsung (in this situation), including Smart Switch, Kies, and other utilities, not only fail to rescue the firmware, but get in the way of ODIN, require resetting your Samsung account additional times, take up hours of bandwidth, ram, proc power, and gigs of hdd space. At best, Smart Switch is horrible, worthless, and stupid waste of time for those with an actual corrupted EFS partition, no backup, tripped Knox, and the other deets mentioned herein.
Hi, guys.
I picked this xt1033 and it had the microusb input damaged, so i replaced it, but since then, it got stucked on motorola logo.
I guessed that the system got corrupted and then i uploaded some new system. It went through nicely, but when it rebooted got stucked again. So, i'ved unlocked it bootloader (to start from zero) and re-locked it, putting a new system from the ground and apparently it ended well, but it got stucked again on logo (and later i've founded that it didn't lock). I've begin to put TWRP to install a custom rom on it (to see if i've could pass throgh that) and founded that my files was still there (EVEN AFTER I'VE UNLOCKED THE BOOTLOADER, who would've erased everything from inside), system, images and even whatsapp files. MTP Service give-me a taste of what was inside and everything was there, nothing corrupt.
So i'ved erased it and put a new rom, TWRP said it did it and was asking for reboot, so i did.
And it got stucked again and nothing was erased.
So the thing is, it's internal storage is freezed and i can't do anything with it.
Could you guys help me? Thanks in advance.
i may be wrong here... but i dont remember unlocking bootloader erased my data.... but it was long time ago...
coming back to your problem.. have you tried using repair option in twrp?
also try wiping all partitions and do a recovery reboot to see if it works
access_unlimited said:
i may be wrong here... but i dont remember unlocking bootloader erased my data.... but it was long time ago...
coming back to your problem.. have you tried using repair option in twrp?
also try wiping all partitions and do a recovery reboot to see if it works
Click to expand...
Click to collapse
Already done.
I could only enter TWRP by boot it on bootloader, not flashing ('cuz was impossible to write on memory and was saying that the flash was successful).
TWRP said it wipe it completely without any error, but it's was there.
And by ordering to reboot on Recovery Mode, it went back to original recovery and trying to erase from there do the same thing (said that was complete, but everything is still there).
Same problem here, this is a problem with emmc bricked
Any time I've tried to restore a backup it has completely bricked my phone. I tried just backing up the default options and restoring bricked, so when I had my phone rooted and setup perfectly with XXX no limits on Android 10 and all my apps installed, I made a FULL backup in case I bricked it with smurf kernel or something. Long story short, I ended up bricking it via other methods and tried to restore my full backup only to be completely bricked again. Not even recovery works after installing a backup. I've found that no matter what I backup, if I restore it it completely bricks my phone to the point where it only automatically boots into fastboot and I have to install a system image and start over every time. Am I doing something wrong or does TWRP 3.3.1-70 not support restoring yet?
jld2k6 said:
Any time I've tried to restore a backup it has completely bricked my phone. I tried just backing up the default options and restoring bricked, so when I had my phone rooted and setup perfectly with XXX no limits on Android 10 and all my apps installed, I made a FULL backup in case I bricked it with smurf kernel or something. Long story short, I ended up bricking it via other methods and tried to restore my full backup only to be completely bricked again. Not even recovery works after installing a backup. I've found that no matter what I backup, if I restore it it completely bricks my phone to the point where it only automatically boots into fastboot and I have to install a system image and start over every time. Am I doing something wrong or does TWRP 3.3.1-70 not support restoring yet?
Click to expand...
Click to collapse
Stop trying to restore the complete backup.
Flash the ROM and restore data only.
I don't see a point in backing up the ROM, when you can just as easily flash it then restore data.
tech_head said:
Stop trying to restore the complete backup.
Flash the ROM and restore data only.
I don't see a point in backing up the ROM, when you can just as easily flash it then restore data.
Click to expand...
Click to collapse
It's just a hassle because installing Android 10 factory image via fastboot fails every time. If I fiddle around and brick, I have to fastboot install Android pie, root it and install twrp, download Android 10, install it via local updater then flash magic to the other slot then reboot and install my xxx no limits module before I can restore my data. Compared to just getting TWRP up and running and restoring my backup I'm looking at a time consuming process to get to that point. I wish I knew why flashing Android 10 via fastboot bricks every time because that's a major cause of this headache while figuring out what does and doesn't work on Android 10. I already have titanium backup backing up nightly to Google drive so by the time I get to the point I can flash my data I might as well just restore my apps + data in TB. If I could get TWRP to successfully restore my backups I'd be given a lot of freedom to tinker around freely without worry of this time consuming restoration. I think next time I'm gonna try backing up into a flashable zip and seeing if I can successfully restore my image via fastboot when I inevitably brick again while messing around
tech_head said:
Stop trying to restore the complete backup.
Flash the ROM and restore data only.
I don't see a point in backing up the ROM, when you can just as easily flash it then restore data.
Click to expand...
Click to collapse
I haven't actually tried this. Are you talking about flashing the rom, and (within the same instance of TWRP), then restoring? Or are you talking about flashing the ROM, booting it, then going back into TWRP and restoring data?
just a quick question?? why are you always downgrading to a9?? when you can simply
1. flash a10 ( i save one on my PC in case a problem arises)
2. set up the phone
3. in pc, open a10 rom, locate for its boot.img amd store in phone
4. install magisk.apk and patch boot img , then copy to pc
5. install patched boot.img via fastboot
congrats,, back on track.. it only took me about 10-15 min to restore a bricked device up to being rooted and twrp installation
If ill root my phone, and delete the browser and the play store for example... and then ill go into recovery mode and make a factory reset, will those app will come back?
If yes, is there a way to prevent simple factory rest to recover those app? ty
A Factory Reset rolls back Android OS to the state as it was pre-installed by OEM/Carrier when they put the phone into the market. A Factory Reset doesn't affect Android's /system partition but only the /data partition. So if browser and Google Play were pre-installed as user-apps ( in /data partition ) then they get restored by a Factory Reset: there is no way to prevent this, AFAIK.
jwoegerbauer said:
AFAIK
Click to expand...
Click to collapse
ty man!
I have another question.. maybe you'll know...
I want to disable the recovery mode, It happened to me once without intention... I hade a Homtom phone, and i rooted him, and then i tried to put TWRP recovery. I didn't succeed, but what happened was a black screen every time i tried to enter recovery mode. that's what im looking for, something like that.. replace the stock recovery with a broken recovery mode or whatever will do the same work.
I know that with an access to my device you can flash a different recovery and thus make it work again , but most people where i live don't know how to do that, and even they don't know to root or even to unlock the bootloader. most people won't know to recognize the problem, they are not so smart.
Of course there are those who know and can do it, but it does add a lot of security to my phone, and besides that there are other reasons I want to do it besides security. What I do not know is how to do it in the simplest way. what happened to me then was by mistake or by luck
Ozakong said:
I want to disable the recovery mode, It happened to me once without intention... I hade a Homtom phone, and i rooted him, and then i tried to put TWRP recovery. I didn't succeed, but what happened was a black screen every time i tried to enter recovery mode. that's what im looking for, something like that.. replace the stock recovery with a broken recovery mode or whatever will do the same work.
Click to expand...
Click to collapse
Flashing TWRP means that device's Stock Recovery unrecoverably gets deleted. As long as you haven't backed up device's Stock Recovery before flashng TWRP means you've lost, IMO, unless you have device's Stock ROM at your fingertips where you can extract the recovery.img from.
jwoegerbauer said:
Flashing TWRP means that device's Stock Recovery unrecoverably gets deleted. As long as you haven't backed up device's Stock Recovery before flashng TWRP means you've lost, IMO, unless you have device's Stock ROM at your fingertips where you can extract the recovery.img from.
Click to expand...
Click to collapse
How can i delete the Stock recovery mode without installing anther recovery instead? i want that my phone will be without recovery mode at all!
If ill just delete recovery.img from my system folder, will it work? In which folder i can find the file "recovery.img"?