I need some help with something. I am trying to restore a backup of one of my ROMs that I created a backup of with CW and I am getting this message after Restoring system "Error while formatting /system!" So now if I reboot it gets stuck at the White screen with the HTC.
Does anyone know what this is all about? Why would I get a formatting system error? If I am stuck how do I get back to original state?
I just tried a test with a different back up and same result.
Finally! Someone with the same issue as me!
It sucks.
Even tried flashing the shipped RUU and rooting/S-OFF from scratch. No dice.
Happens with any version of CWM I use.
ProTekk what are you doing now with the phone? Has anyone else given you an explanation? Have you tried to go original out of the box state?
Just reflashed the custom RUU and re-rooted.
Not ideal, but it keeps S-OFF and gives me a working phone.
Grab the RUU file, rename it to PG05IMG.zip, and place on the root of your sd card. UNPLUG the phone and turn it off. Restart the phone UNPLUGGED while holding the volume down toggle. It will flash the RUU to your phone and return it to stock, unrooted, S-On.
Reroot using the instructions from the team.
Been there, done that, got the t-shirt...
This happened to me today too... i reflashed the last ruu file in the rooting directions, reran the last few lines of code and went from there. Then after having superuser installed, and rom manager installed, i verified root and then rebooted into clockwork and installed my old backup. No big issues. Just sucks i had to go through that again.
This happened to me when i tried getting rid of that new virus rom. Not that it was bad, just didnt like the 'flavor'. So i went into cwr cleared data then tried to install my previous backup. That's where it all went to hell.
/\\/\\orlince
Just wanted to let you know I was successful is just flashing a .zip of any ol rom that you can find on the site, I used Lightning v1.2 to flash CWM and then rebooted into recovery and recovered from one of my backups. Hope this helps!
-Justin
I am an desparate need of some help. I was trying to take care of a friend's Moto G. It is an XT1034. I went to flash TWRP and somehow the installation broke. I am unable to get into recovery. After that happened, I decided to restore back to stock. I downloaded the latest image on the index post, and followed the guide to restore it. I went through each piece correctly. Now, I am not able to get the device to boot. When it attempts to reboot, the recovery will flash for about half of a second, and then restart. I AM able to get into fastboot, so I should be able to fix this. However, I am not quite sure how to continue at this point. I am going to redownload the image, just to rule out a bad download. However, other than that, I am not sure how to solve this. Any advice?
EDIT: Redownloaded the images and checked MD5, passed. Also tried downloading an earlier image (5.0.1), and it will not flash.
OK. I have been working on this for hours, and I have some info. I built a batch file using House of Moto. After flashing that, I still was getting the problem with the recovery popping up for a split second, before restarting. However, if I choose QCOM in the fastboot menu, the device will boot. The partition table has to be messed up. Flashing the gpt file does not change this. Does anyone have any ideas?
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.
Hey all,
I'm not a total noob, but I do this so infrequently that I can't commit it to memory. Would really appreciate some help here.
I followed the official LineageOS Guide for Herolte, over here.
I had done this previously on my Nexus 7 so I was fairly confident.
Everything worked well, I got TWRP installed using Heimdall from Linux, and successfully pushed the latest LineageOS and open_Gapps images to the phone.
Rebooted into TWRP, and followed the recommendation to wipe System, Cache and data partitions. This failed with red text stating that ti was unable to mount data.
I googled some, and found a suggestion to reformat the partitions, first to a different file system and then back to their original file systems again. I tried formatting /data to exFat, and it took forever, eventually erroring out with an error message. After this I can't get into TWRP anymore. When I try the phone boots to the TWRP startup screen, and just freezes there.
I have tried reflashing TWRP using Heimdall and this does nothing. Flash succeeds, nut still freezes at TWRP splash screen.
I googled some more and found a suggestion to flash stock Samsung firmware, and then try again, this time formatting data system and cache without trying to first wipe them. Problem is I can't successfully flash stock firmware.
I tried using this method in Heimdall, but it complains "Local and device PIT files don't match and repartition wasn't specified!" and fails.
I've also tried booting into Windows and using Odin, but it never works. The screen turns grey, and no progress indicators ever start. I assumed this was because I had the incorrect drivers for the phone, and tried using zadiag.exe to replace them, but the driver install fails.
I'd greatly appreciate any help. I can't seem to force the phone to shut off, it just keeps rebooting and getting stuck on either the TWRP spash screen or on the download mode screen. I know this is solveable, but unless I figure it out fast, I'm worried I am going to burn in the screen.
Any suggestions appreciated!
Never mind. I must just have had a bad stock image.
I downloaded a different one, and retried heimdall and it flashed properly.
I am now able to re-flash and boot into TWRP again.
Hopefully I won't have the same problem again when I try to wipe the partitions...
Alright,
So I solved this issue by (once I reflashed stock, and then reflashed TWRP again) formatting the data partition twice, first to ext3, and then back to ext4. This looks to have cleared the encryption issues that were causing thsi problem ,and allowed everything to continue working as expected.