Related
Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
I also tried to flash it with .pit, PDA, PHONE and CSC. I got this screen and then stopped and Odin says "Now Writing, Please wait about 2 minutes."
I appreciate your help!
same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!
TML1504 said:
same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!
Click to expand...
Click to collapse
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!
davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!
Click to expand...
Click to collapse
again thx,
but the problem is seems to be "deeper" than only a corrupt /data!
The tab doesnt boot further then "samsung 7.7", if data is corrupt then
at least android will load (bootanimation) and go into a bootloop in some stage!
Also, I didn't change or install or flash anything in rom-manager, I "only" used the reboot function!
After reflashing the device with repartition and HongKong.pit I think I messed up the partitions totally, so I would really need the PIT for 6810 (6800 has different partition layout) to repair this!
But as it seems no one has this PIT or is willing to provide it,
so I ordered an new tab which will arrive in the next hours, and return this one within the next days!
Where did you find the PIT file ? You may just destoried the partition. God bless you!
matth3w said:
Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
Click to expand...
Click to collapse
I have a familiar problem....
I have not flashed or rooted my device - it is exactly how it came out of the box...
One morning while using it it froze - I did are reset by holding the power button down and then let it reboot but when it did it can not get past the "Samsung Galaxy Tab 7.7" screen.
Can get it into download mode, but if I go to recovery mode then all I get it a headline saying "Manual Mode" which grabs some manual .apk files and then just goes back into the boot mode with the "Samsung Galaxy Tab 7.7" screen.
Any ideas?
Had a Galaxy Tab Original and got the Galaxy SII and have mod them to death - just though for this one I would leave it original and enjoy the OTA updates as the were delievered - especially considering ICS in a matter of days
If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
suwandiapr said:
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
yes, that is what he means.
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem.
Obviously you will lose all user data!
suwandiapr said:
If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!
davp said:
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem!
Click to expand...
Click to collapse
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.
Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
Yes you right, thats what i mean..
TML1504 said:
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!
Click to expand...
Click to collapse
Im sorry , my answer cannot solve your problem.. You say your device "stuck on Samsung logo" right? your recovery and download mode seem ok, from my experience its because /data corrupt or something crash on your filesystem..
If you can go to recovery menu, do factory reset,..
I cannot help you with pit.file coz i actually dont have the device right now..
Aspi914 said:
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.
Click to expand...
Click to collapse
Good luck..
davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
Click to expand...
Click to collapse
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?
白い熊 said:
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?
Click to expand...
Click to collapse
You either get it from a full flash of stock firmware, or make your own tar with just recovery.img in it (extracted from stock). And flash with odin in the pda.
It is handy to be able to switch recoveries. CWM doesn't seem to match the 3e data wipe/factory reset.
The problem was:
I was playing a game, in the middle of it the Tab reset, I've never had it reset. Then it rebooted to the Samsung Tab 7.7 logo.
I thought, I'm lucky, made a CWM backup. So tried to restore the CWM backup. When the restore got to /data the tab rebooted again, i.e. something was messed with it.
So got stock firmware, flashed it from PC odin, flashed with success. But rebooted to the logo again.
Tried to get into the stock recovery, but it would only show "Updating..." something, I don't remember anymore, but the stock recovery wouldn't boot. Flashed it a couple of times, same result. Had to take the Tab back to the store...
Am kinda afraid to mess with it now, since I don't want it to happen.
So am wondering what to do if the same happens, or just forget CWM and flash stock recovery.img just to be safe?
I had similar issues after hard power-off [long hold power button]. Confirmed with adb into insecure cwm recovery that /data was corrupt. It explained why my restores stopped at /data.
Cwm data wipe, or format data did not help.
I flashed the stock 3e recovery.img in a tar with odin.
3e data wipe/factory reset. Reflash whole stock firmware with odin.
Check system boots ok.
Reflash cwm, then do restore ok.
I have seen stock 3e recovery fail to start properly. It seemed to be related to files/directories on the external sd card. It came up and said something like 'manual mode', 'updating'.
I tried clearing cache and hidden.
I know I deleted at least tmp_sec_fota directory off the external sd card, maybe someting to do with fota is upsetting our tabs from time to time.
Yep, exactly, that's it, it was "Manual mode" and "Updating", same symptoms, I couldn't get past it.
So what you're saying, I had a MicroSD in it, and that's why it was stuck at this? Not sure if I had an SD in it, but I flashed stock like three times, and then still couldn't enter 3e recovery, all the time had this "manual mode" come up...
Thanks for the guide of what you did.
Am downloading the latest Thai firmware now, to extract the stock recovery, so that I'm ready just in case.
Do you just tar the recovery.img and use that for flashing if necessary? No special permissions, nothing?
Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd. It is possible the problems are in multiple locations,
It is also possible that multiple attempts have an effect.
I personally feel I need both stock 3e and insecure cwm [and odin and adb] to be able to recover this tab. The broken 3e/reboot was my worst experience on this so far.
Use linux tar or the tab's busybox tar, to create an uncompressed tar with recovery.img as the only file. Do not use 7zip to create the tar, it didn't work for me (although it works fine to extract from the stock).
davp said:
Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd.
Click to expand...
Click to collapse
You mean you did this in CWM recovery? Because I hastily flashed the stock ROM when it wouldn't boot, and then I couldn't get into the recovery anymore and there was no way to flash CWM recovery from PC Odin, or is there?
SD you mean internal? Since with external you just pull it out...
This was my worst experience as well, and want to be ready if it ever happens again.
So to sum it up. If the /data is messed up, should we do the following?
1. In CWM recovery clear cache, clear hidden.
2. Flash stock e3 recovery.
3. In stock recovery wipe everything.
4. Flash stock ROM.
5. Boot.
6. Flash CWM recovery.
7. Restore backup.
please i have the same problem,where i find the stock e3 recovery?
thanks Davp!
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
please,post a link for download the recovery.img tar for to flash with odin.this is my last hope!
Hello everyone. So, let's start by explaining what I have did.
For a while I had the XtreStolite Odex 2.0 edition and I wanted to try out other ROM. I have factory reset-ed when I was installing the ROM using TWRP and I somehow managed to delete all the phone's internal stuff, but I can still boot to TWRP or download mode.
I have tried to flash stock firmware using Odin 3.10.6 ( running as administrator too ) and when it gets to sboot.bin it fails right away. I have tried using Samsung Smart Switch PC Software, tells me my device is unsupported. If I try to manually find my model using the S/N, the software fully downloads then gives me an error.
I have tried to ADB sideload from TWRP Advanced menu, whenever I want to flash for example xtrestolite odex zip ( named rom.zip for short ) it goes "serving:... 21%" and gets stuck. If I try to push a zip it says "error:closed". I am no big expert in ADB, I don't know how to install the latest version, and I can't download the full Android SDK because my internet is very slow. I had Bootloader and Modem 5.1.1
I am looking for a way to move the XtreStolite ROM zip into the phone's memory so I can boot to TWRP and install the ROM. I've seen something with OTG Cable and USB but I have no real knowledge of these. If it comes as a last resort, if someone could briefly explain me how would I manage to repair the phone using the OTG Cable and USB stick.
I also have a Nandroid Backup on my PC but I don't know how to move it to the phone's storage, because it's well, bricked. When I'm trying to copy files over Mount option in TWRP, it says that it cannot copy the file, the device may be disconnected.
I had Bootloader and Modem 5.1.1, also Windows 10. I can go back to 7 or 8.1 anytime it's needed.
Much appreciations.
EDIT: I actually repaired it by flashing a stock firmware downloaded from xda ( God bless you whoever linked the mega.co.nz stock fw link ) . Thread can be deleted.
You can also flash these via odin.
http://www.sammobile.com/firmwares/database/SM-G920F/
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.
I've tried flashing the Unknown (XAS) version of the N920PVPS3DRD1 firmware coming from the N920PVPS3DRD1 Sprint (cdma) Through odin. It got stuck on finding pit file, so I closed odin and now my device is stuck in a bootloop. It stays on samsung galaxy note 5 screen then restarts and goes to TWRP. When I go into download mode it doesn't display any information in the top left. I have a backup of the sprint version which I have tried restoring to (I haven't wiped any data in fear of losing the backup) However I have the backup on my PC too which I should be able to send to the device using ADB. This didn't work. And it is still stuck in a bootloop. Does anyone know how to solve the issue? Thanks.
Download the correct 4 file package(I like Android File Host) and reflash using Odin. Edit the Odin .ini file to unlock all of the options, and then make sure you check the boxes that say nand wipe, phone efs clear, and bootloader update. Also extract the .pit file and insert that into the pit section. If it doesn't flash fully the first time, uncheck all of the boxes, reboot Odin mode, and flash again. This almost always solves my flashing issues.
I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?
pr10dr said:
I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?
Click to expand...
Click to collapse
You just need to flash the latest G930F for Germany. The firmware code is DBT, it's unbranded so no netweork provider bloatware.
I've attached Samfirm tool. It gets the latest firmware straight from samsung servers version 8.
1. Unzip
2. Run application as admin
3. Check auto box
4. SM-G930F in Model box
4. DBT in Region box
5. Check Update
6. Wait to finish
7. Flash files with Odin
8. New Phone.
I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6
Alright i think i resolved part of the issue as follows:
* i flashed the complete stock firmware as described above
* After flash was done i rebooted again into download mode and installed TWRP as recovery via odin
* I then booted into TWRP and copied the "no-verity-opt-encrypt" in the latest version to the phone
* The zip of "no-verity-opt-encrypt" i then installed with TWRP.
The phone booted up. Factory Samsung Android works but the imei is still shown as empty / unknown.
Some guides suggest to flash a factory combination image but i can not find one for bootloader version 8 which is on my phone.
pr10dr said:
I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6
Click to expand...
Click to collapse
Yes sometimes this happens, try a different firmware like United Kingdom BTU.
Does Odin say Pass?
The updating and erasing screen is normal after flash just leave it.
Once the phone boots on BTU you can either change language to German or flash DBT again.
It's worth checking / reinstalling Samsung drivers. Use different USB port. Odin should be version 13.
As long as you can boot into download mode the problem is fixable.
Thanks for your advice.
I will try the BTU firmware later. Just to check we are on the right track: If i understand you correctly you are saying the lost imei will be "fixed" by installing either the BTU or DBT stock firmware via odin?
Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.
pr10dr said:
Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.
Click to expand...
Click to collapse
OK it sounds like the BL info on the EFS is missing or corrupt.
Just try one more thing before trying to repair the EFS.
Flash firmware again with Odin but uncheck "auto reboot"
When passed in Odin disconnect phone.
Hold volume down+home+power. As soon as the screen goes back move your finger to volume up while still pressing home +power. You want to boot into system recovery. It may take a few attempts.
Once in system recovery, wipe data/factory reset and reboot phone.
Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated
pr10dr said:
Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated
Click to expand...
Click to collapse
Anyone offering money to fix or connect to a server is a scammer, stay clear.
To repair the EFS you have to get the stock firmware back on there or flash someone esle's EFS back up file. You can buy a damaged S7, install TWRP, back up the EFS to the SD card, put that sd card in your phone then restore the efs. Your phone will then take on the identity of the phone the EFS file came from. Effectively you will have a new IMEI number and mac address. As long as the donor phone is not registered on the network your phone will work fine. You cannot have two phones with the same IMEI registered on the network, both will be blocked and black listed. Obviously the donor phone must be exactly the same model as yours.
However the method below should be tried first.
The error with the text "failed to open recovery" means the phone cannot find the partition where the stock recovery file is located.
Now to solve this we can install TWRP with ODIN and that will provide a way to install the stock firmware in .zip format direct from the sd card using TWRP as the recovery method instead of the inbuilt stock recovery which cannot be found.
You should then be left with a phone which has a restored EFS with your original IMEI and other data with TWRP as the recovery tool.
Which ever method you choose TWRP must be installed first.