Database Users

[ROGERS SGH-1337M] Wont Reboot Without FULL WIPE

INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!

Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Which ROMs are you installing? On I337M your best bet is T-Mobile ROMs and Kernels. I have Bell I337M and have no issues.

Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping

kiru said:
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping
Click to expand...
Click to collapse
i just went through this all last night what a pita , problem is twrp , if you do a full wipe when you type the word yes , you can only bootup 1 time then it gets stuck next time you boot , theres no way to fix it , even going back to old version of twrp wont do it , you have to compleatlly remove root and return to stock , re root and install twrp again , then if your luck your nandropid backup will work , it took me 5 hrs to fuger this all out , stupid twrp drove me nuts .,...
in short , return to stock and reroot , then never do a full wipe where you have to type yes

Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
i had the same problem, im with rogers so i downloaded the rogers rom 4.2 and i cant make any phone calls or listen to music or watch videos. my phone came with 4.3 does anyone have any ideas to help me?

No Data Samsung Xcover 2 GT-S7710L -- Latin Version

This all started when I ran out of data on my device and decided to root it so that I could use the SD card. I had previously rooted a droid 2 and a galaxy nexus so I wasn't a complete noob but I'm not in any way a programmer and I had never used Odin. So not wanting to mess with things without having a back up I followed some tutorials and downloaded the android sdk and used adb to back up. I thought I was doing a full system backup but whether I made a mistake or this simply doesn't back up everything I don't know. The file size should have been a clue but I missed it. I did get my apps
I then proceeded to follow the tutorials on this site for rooting the device. They are all for the GT-S7710 but I was hoping the letter (L) was a program only type thing and wouldn't make a difference. I used this guide http://forum.xda-developers.com/showpost.php?p=40232503&postcount=45 and downloaded the DEODEXED Version. I then rebooted the phone and everything appeared to be working fine and I was rooted. I could have sworn I had data. I then realized that I didn't have CWM as a recovery so I downloaded and installed CWM recovery http://forum.xda-developers.com/showthread.php?p=43294839 It was after rebooting (and maybe a reset I can't remember at this point) that I noticed I had no data.
So I flashed a few other ROMs including VANIR (and the recovery he suggests) http://forum.xda-developers.com/showthread.php?t=2689519 I and CM 11 plus a stock rom (S7710LUBAMC1_S7710LUUBAMC1_CHO Samsung kies tells me CHO is the region for my device) but didn't have mobile data in any of them.
Still hoping to get mobile data working again I flashed a stock Recovery and A stock Boot.img from here...(Well I can't seem to find the thread now). It was a link to the stock boot.img and stock recovery.img (GT-S7710) from someone wanting a CWM recovery built. I then reflashed the stock ROM from above still no mobile data. My flash count in download mode is up to 26 lol and nothing I have tried restores the mobile data although as long as the phone boots, I do have wifi.
Is there ANYthing else I can try? I would really like to have my mobile data back even if it means I don't get to root.

No data connection
It turned out my no data was caused by not having any APN settings after flashing the custom ROM. I copied the settings from hubbies phone and now data works fine. I can't believe I spent so much time working on this and trying different things when it was something so simple.

Fix for people with a corrupt EFS (No network connection or bluetooth)

A few people have had issues with the EFS getting corrupt or wiped on their OPO before they had a working backup. This guide has so far worked for 4 people to restore their EFS allowing them to access mobile data and bluetooth again.
Note: I really don't know why this works, I have contacted the dev of this rom to ask if he has any ideas but still waiting on a response.
1. Flash official TWRP
2. Flash this ColorOS rom using TWRP - http://forum.xda-developers.com/showthread.php?t=2772627 (you can skip all the account setups if you want)
3. Factory reset
4. Boot and setup ColorOS (you should see a network connect now with your sim card inserted, you will need to toggle mobile data on to test that)
5. If you have data in ColorOS you are good to flash back to CM11S anyway you want (you will need to factor reset after flashing back)
6. Save yourself the headache in the future and backup your EFS
Please post if this fix works for you.:victory:
Edit: I've went ahead and downloaded the ROM and I will hold on to it incase the original mirrors go down for some reason. Please PM me if they do.

One of the ones who can confirm this works. Will post in the official thread.

Worked for me also.

Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now

tw1tch175 said:
A few people have had issues with the EFS getting corrupt or wiped on their OPO before they had a working backup. This guide has so far worked for 3 people to restore their EFS allowing them to access mobile data and bluetooth again.
Note: I really don't know why this works, I have contacted the dev of this rom to ask if he has any ideas but still waiting on a response.
1. Flash official TWRP
2. Flash this ColorOS rom using TWRP - http://forum.xda-developers.com/showthread.php?t=2772627 (you can skip all the account setups if you want)
3. Factory reset
4. Boot and setup ColorOS (you should see a network connect now with your sim card inserted, you will need to toggle mobile data on to test that)
5. If you have data in ColorOS you are good to flash back to CM11S anyway you want (you will need to factor reset after flashing back)
6. Save yourself the headache in the future and backup your EFS
Please post if this fix works for you.:victory:
Click to expand...
Click to collapse
Hi, i failed and i wiped EVERYTHING of my phone, i only had the fasboot mode, i installed CWM and the cyanogemod rom, now everything works, and i have the imei in the box, however, i dont have the possibility of EFS backup anymore.... any ideas..?

Gambalajillo said:
Hi, i failed and i wiped EVERYTHING of my phone, i only had the fasboot mode, i installed CWM and the cyanogemod rom, now everything works, and i have the imei in the box, however, i dont have the possibility of EFS backup anymore.... any ideas..?
Click to expand...
Click to collapse
Official TWRP doesn't have EFS backup in it, you have the get the unofficial one http://forum.xda-developers.com/oneplus-one/development/recovery-unofficial-twrp-2-7-1-0-t2815247
Yank555 said:
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
Click to expand...
Click to collapse
Odd, maybe you could try using TWRP to delete everything again including system, then sideload and boot ColorOS.

tw1tch175 said:
Official TWRP doesn't have EFS backup in it, you have the get the unofficial one http://forum.xda-developers.com/oneplus-one/development/recovery-unofficial-twrp-2-7-1-0-t2815247
Click to expand...
Click to collapse
To add to that you can just boot the unofficial recovery using "fastboot boot recovery.img" to do your efs backup if you would prefer to keep the official TWRP installed. That way it only boots that recovery to allow you to do the backup of your EFS partition and doesn't erase your current recovery. That's how I did it.

sabbotage said:
To add to that you can just boot the unofficial recovery using "fastboot boot recovery.img" to do your efs backup if you would prefer to keep the official TWRP installed. That way it only boots that recovery to allow you to do the backup of your EFS partition and doesn't erase your current recovery. That's how I did it.
Click to expand...
Click to collapse
WOW thanks, i do it and and i tell you how did it go in a few minutes.

I see that the OP has been thanked and this thread has a few success stories so I am giving it a bump for others to view in case of the same issue.

I just flashed the factory image... I never had the problem again

Yank555 said:
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
Click to expand...
Click to collapse
Im having the same problem as you have Yank555. It started with the AudioFX FCs rendering the device useless.
Next i tried to reflash the standard CM11s 25R rom back to get my phone normal again, it didnt work.
Then i remember i have a nandroid from a few days ago. Not thinking to read up on known issues with the OPO EFS i tried a restore.
My EFS is gone and the phone will not work unless im on ColourOs120. Wifi doesnt work, just basic phone functions.
Still waiting for a miracle for this problem.
Any suggestion guys?

jwai85 said:
Im having the same problem as you have Yank555. It started with the AudioFX FCs rendering the device useless.
Next i tried to reflash the standard CM11s 25R rom back to get my phone normal again, it didnt work.
Then i remember i have a nandroid from a few days ago. Not thinking to read up on known issues with the OPO EFS i tried a restore.
My EFS is gone and the phone will not work unless im on ColourOs120. Wifi doesnt work, just basic phone functions.
Still waiting for a miracle for this problem.
Any suggestion guys?
Click to expand...
Click to collapse
Did you open a service request ? Any response ? So far all I got 5 days later was a "please fastboot flash factory images, case closed." which quite obviously did not help, so case reopened, but again nothing from them in 4 days, now.
But I wonder if my first thought is still correct, flawed emmc as flashing seems to work ... might be a radio hardware issue ? Just don't quite get what the AudioFX has to do with that... cause simply rooting the device and installing apps and making a few nandroid backups is no way to brick anything.
But anyway, tbh, OnePlus is mostly dead to me as a company, worst invest ever so far, nice if your device works, but service is not even close to bad, it's pretty much non-existing ... and for a supposedly "best service ever" it's quite, let's say, "impressing"
JP.

Nope, i have not tried opening a ticket, mine is a grey import from China.
There is something terribly wrong somewhere hardware wise. The audiofx problem only happens if i flash the CM11s. After ColourOS i have tried flashing the CM11 M8.
Im also wondering if i should try to use this OPO made rom to see if it can help.
https://forums.oneplus.net/threads/rom-official-4-4-4-oneplus-aosp.65482/

jwai85 said:
Nope, i have not tried opening a ticket, mine is a grey import from China.
There is something terribly wrong somewhere hardware wise. The audiofx problem only happens if i flash the CM11s. After ColourOS i have tried flashing the CM11 M8.
Im also wondering if i should try to use this OPO made rom to see if it can help.
https://forums.oneplus.net/threads/rom-official-4-4-4-oneplus-aosp.65482/
Click to expand...
Click to collapse
Give it a go, not much to lose. Didn't work for me, though.
JP.
Sent from my Nexus 5 running stock rooted AOSP on Yank555.lu v1.0-alpha5 kernel.

This worked for me! I'm back in business! Thanks guys for getting this figured out, I thought my phone was done.

I hate to bring this back up.
I have a Nandroid of my stock CM11S on my phone. I used it for the update to 300 to get firmware, then made a backup of it and went back to the custom Rom I had been on.
Today, I went and restored the backup of CM11S to sideload the newest update. Weirdly, after restoring I have an unknown baseband. But if I go back to the custom Rom backup I still have a baseband.
I wonder if TWRP just didn't backup the correct partitions? I am on the offficial TWRP. But I do have a backup that contains my EFS backup from the other TWRP that has that option.

I think I know what corrupted my efs....I used the official twrp 2.7.1.1 which for some reason saves modemst1. I remember restoring st1 when I corrupted it the first time with the official 2.7.1.1. Well I did it again trying to restore a nandroid with the official twrp 2.7.1.1. Do not restore the saved modemst1 from the official twrp 2.7.1.1. You will encounter problems.

So, this same thing happened to me...i happily using 30O and not really any issues and getting good battery life~17 hrs w/moderate use. And no other bugs.
Found the 33R update here on the forums and downloaded it and flashed through TWRP.
Thats when trouble found me, lost network and wifi stuck trying to turn on but never finds wifi. Then reading through xda someone suggested to check IMEI and it was gone. I had NOT done any prior back ups other than Nandroid prior to flashing update.
Restore still didn't fix it.
I tried this (flash ColorOS and CM11) but still didnt fix it. I was bummed as my OPO is very new and I had been happy with it.
CM11 or by restore, windows will not detect it even with drivers loaded. Flashing colorOS would allow windows XP to recognize internal and allow me to send files so i tried custom ROMs and CM stock and Mahdi but none worked. Luckily my TWRP still works and i am able to boot and get into fasboot.
I finally got mine fixed with rooted stock 33R from here on xda!
Now my OPO is back in business!!!

Save st1 and st2 with vonnegut's method http://forum.xda-developers.com/showthread.php?p=54623075.. Put it in a safe place for later. I uploaded them to google drive and onedrive . It saved me today.

For those of you that were able to recover, did you lose your entire EFS folder? Mine is completely gone and I don't think this ColorOS trick works either. I've tried it all last night and I fell asleep at my desk

Easy Lollipop 5.1 downgrade to KitKat 4.4.2 with TWRP - maybe

If you want to read the below learning experience you may gain some knowledge but at this point I believe my method may have flaws. While it seemed fine at first the problem listed directly below could not be fixed without using Odin to flash a stock ROM back onto the phone. It had checked the hidden menu settings for MTP and ADB and PDA, CP etc and all were correct (I have another good working S5 to compare these values to). I tried an earlier restore of a TWRP backup and that just blew up with all sorts of FC's on boot. So thank goodness for Odin. After flashing the stock rom it booted fine and I can now write files from the PC to the phone again via USB. In the process right now of re-rooting, installing TWRP and doing a restore of my last backup.
Note : I have found one problem I am currently working on after using this method. I can hook up the phone to the PC and get a link, open folders on the phone and can copy file from the phone to the PC but can NOT copy files from the PC to the phone. More later .....
I've got a Samsung Galaxy S5 from US Cellular. Other than a few people in the Motorola subforum here trying this I haven't seen this exact method described here so apologies if I missed it somewhere - tried many searches. It seemed so easy - maybe it is just considered SOP for some - don't know so I'm going to run the details by here anyway in case it saves anyone some trouble. Do read my warnings below though before you attempt this.
1 - You want TWRP installed (or Philz CM Touch will probably work too - seems a bit more complex though) If you are flashing ROM's having TWRP or some other custom recovery is always a good idea and I'm sure most people have one of them.
2 - Always do a complete backup with TWRP before flashing anything new. You did a backup before going to Lollipop didn't you?
3 - So you are tired of the white screen, battery sucking, quirky Lollipop or maybe that Cyanogen Lollipop mod didn't quite work for you and you want the old Kitkat back. So fire up TWRP, go into Advanced wipe and wipe Dalvik Cache, System, Data and Cache. You aren't done wiping yet though. After you swiped to wipe those go back to the previous page and Swipe to Factory Reset. That may not actually make any difference but I just did it for good measure and my method worked great.
4 - Now without out even needing to reboot find your latest backup of Kitkat 4.4.2 that you have on your Internal SD or External SD card (you do keep one there don't you in case your phone glitches on you while you are out and about?)
5 - Do a Restore of everything - Boot, Recovery, System, Data, Cache.
6 - Reboot. You are done.
Firstly I need to add that I had flashed Cyanogen Mod 12.1 (Lollipop 5.1) after following directions here in the main Cyanogen subforum to flash that on my KitKat 4.4.2 Galaxy S5 phone. What may be noteworthy is that after flashing CM 12.1 I ran the App PhoneInfo Plus (made mostly for Samsungs) and the OS version showed as Lollipop 5.1 but some of the build numbers to my recollection showed 4.4.2. So this was not a stock Lollipop OTA - it was the Cyanogen mod of Lollipop made by developers here. I just assumed they started with Lollipop to make that latest 5.1 build but I haven't followed the Cyanogen mod much at all so I don't know if they have borrowed bits and pieces of Kitkat in their builds. If they have done that then this downgrade method may not work the same for an OTA Lollipop.
Another warning - I noticed in the Motorola subforum here that some people bricked their phone trying this type of downgrade with TWRP however I believe that is because they had Verizon phones with locked bootloaders and that is not the case for my phone (US Cellular) or any other phones beside VZ as far as I know. If you have a Verizon with locked bootloader beware! I will also add that on my first boot after restoring Kitkat 4.4.2 that the second the home screen was up I started quickly scanning through my app pages and the phone rebooted itself. I believe it wasn't fully done loading the OS and it just was a hiccup. It has not happened since after trying all sort of things. Everything is working great.
I saw most people recommending to use Odin to flash a stock Kitkat firmware back on the phone in order to downgrade from Lollipop. Then you need to re-install all your apps or maybe do a restore of a recovery but with this method using TWRP you bypass most of that and get it all done in one TWRP session.
Another note about what I read people having a problem with upon downgrading - some were losing their IMEI when using Odin to flash the original firmware. I still have my original IMEI with no problem. That is another reason I think this method may be better than using Odin for this downgrade. I'll add that there are a lot of people around here with a whole lot more knowledge about flashing and custom ROM's than me so don't take my ideas as hard fact without doing your own research for your particular phone and particular situation.

I can copy FROM the internal and external SD card to PC but not PC to either internal or external SD card and the permissions seem to be correct for the folders I'm trying to copy into. Anyone have any ideas on that? However I was able to use AirDroid (Wifi) to copy files to the phone from the PC - no real surprise there but it reaffirms that I can write to those folders - just not with the USB cable.
More info. I just decided to run the App KitKat external SD Card patch. It failed. I believe I ran that before flashing Lollipop and it worked but now it fails. ?? I don't know if it is related to this problem since both internal and external SD are having a problem - but only via USB.

I tried another Galaxy S5 with same computer and cable and that one works fine to copy to the SD cards so that eliminates the cable or computer. AirDroid - Wifi works but only a problem one way with USB - WTF?

droidzer1 said:
I tried another Galaxy S5 with same computer and cable and that one works fine to copy to the SD cards so that eliminates the cable or computer. AirDroid - Wifi works but only a problem one way with USB - WTF?
Click to expand...
Click to collapse
Well thanks to TWRP AND Odin all is well once again in Androidland

S5, Flashed TWRP and custom ROM, restored stock from another phone, how to unmess?

Hello.
This is my first post as I've done everything myself till now, but now I'm really lost in some uncharted territory.
All I wanted is to have a second DeGoogled phone and I messed my Samsung Galaxy S5 beyond my understanding
So, I flashed TWRP to my SM-G900F klte through Odin and then installed /e/ ROM through zip method and everything was working fine, then I wanted to flash Intelli kernel, but I got an error saying "Digest failed to match on '/external-sd/Intelli-Kernel-v15-klte.zip'. E: Aborting zip install: Digest verification failed. Error installing zip file '/external_sd/Intelli-Kernel-v15-klte.zip'". I double checked the md5 of TWRP, /e/ and Intelli Kernel zip's, reflashed TWRP, flashed IceMan's TWRP recovery, wiped all partitions, formatted data and re-installed /e/, tried Havoc ROM, but I still got the same message. The problem wasn't only with the kernel, but also with some (not all) other zip's like A2camforS5_TWRP_v1.4.zip and even Magisk (which flashed fine) modules like A2camforS5_Magisk_v2.zip were not flashing (the procedure got through, but once the phone restarted the module wouldn't show up). On my previous SM-G900F klte phone everything was working fine. (And yes, TWPR's check md5 option was disabled, so this wasn't the problem)
After a bit of chatting on Intelli kernel and /e/ Telegram support groups I found out it wasn't the kernel or /e/ problem and that I should go back to stock and start all over. I had a full NANDroid backup from my previous phone so I renamed the backup folder to match the new phone serial (so it would show the partitions to restore in TWRP) and as I (and nobody else) didn't know where the problem was I restored all partitions. Everything went through as it should except modem, which showed an error saying something about being read-only and efs, which went half way through and then gave an error I don't remember (but can reproduce if needed). The phone wouldn't boot to OS (it was stuck on SAMSUNG logo), so I re-flashed TWRP and /e/ again and tried to flash the kernel or other zips but they were still giving me "digestion" problems... but it got worse! Now when I boot to /e/ I'm not even able to use the phone normally as a pop-up saying "Bluetooth app has crashed" and "Bluetooth app keeps crashing" shows up continuously even if Bluetooth as other wireless connection work just fine. Did I mess something up with the unfinished efs restore?
How can I diagnose the problem and unmess my phone? What steps should I take? I'm afraid of bricking my phone if I just start to do random stuff so any useful information would be appreciated! Please help!
EDIT: Even if my description of the procedure looks like I flashed a ton of stuff all at once I have just WRITTEN A RESUME AS CONDENSED AS POSSIBLE - the procedure took me more than a week of flashing ONE THING AT A TIME and testing if everything works fine. At no point in my flashing procedure there were more than three things present on my phone: TWRP, ROM and MAGISK as kernel and camera mod refused to flash anyway. To exclude Magisk being a problem I clean installed everything so I had just TWRP and ROM and I was getting the same problem. Then I reflashed TWRP only, using the IceMan version (because it presumably solves all flashing problems) retested, then flashed /e/ only, retested, Havoc only, retested... well, you got the picture!
I was doing everything under the guidance of Intelli kernel Telegram support group members until I understood the problem was not the kernel, nor TWRP/IceMan, nor /e//Havoc and went with the stock recovery through TWRP and messed my phone beyond Intelli kernel Telegram group's scope.

ShalaMala said:
Hello.
This is my first post as I've done everything myself till now, but now I'm really lost in some uncharted territory.
All I wanted is to have a second DeGoogled phone and I messed my Samsung Galaxy S5 beyond my understanding
So, I flashed TWRP to my SM-G900F klte through Odin and then installed /e/ ROM through zip method and everything was working fine, then I wanted to flash Intelli kernel, but I got an error saying "Digest failed to match on '/external-sd/Intelli-Kernel-v15-klte.zip'. E: Aborting zip install: Digest verification failed. Error installing zip file '/external_sd/Intelli-Kernel-v15-klte.zip'". I double checked the md5 of TWRP, /e/ and Intelli Kernel zip's, reflashed TWRP, flashed IceMan's TWRP recovery, wiped all partitions, formatted data and re-installed /e/, tried Havoc ROM, but I still got the same message. The problem wasn't only with the kernel, but also with some (not all) other zip's like A2camforS5_TWRP_v1.4.zip and even Magisk (which flashed fine) modules like A2camforS5_Magisk_v2.zip were not flashing (the procedure got through, but once the phone restarted the module wouldn't show up). On my previous SM-G900F klte phone everything was working fine.
After a bit of chatting on Intelli kernel and /e/ Telegram support groups I found out it wasn't the kernel or /e/ problem and that I should go back to stock and start all over. I had a full NANDroid backup from my previous phone so I renamed the backup folder to match the new phone serial (so it would show the partitions to restore in TWRP) and as I (and nobody else) didn't know where the problem was I restored all partitions. Everything went through as it should except modem, which showed an error saying something about being read-only and efs, which went half way through and then gave an error I don't remember (but can reproduce if needed). The phone wouldn't boot to OS (it was stuck on SAMSUNG logo), so I re-flashed TWRP and /e/ again and tried to flash the kernel or other zips but they were still giving me "digestion" problems... but it got worse! Now when I boot to /e/ I'm not even able to use the phone normally as a pop-up saying "Bluetooth app has crashed" and "Bluetooth app keeps crashing" shows up continuously even if Bluetooth as other wireless connection work just fine. Did I mess something up with the unfinished efs restore?
How can I diagnose the problem and unmess my phone? What steps should I take? I'm afraid of bricking my phone if I just start to do random stuff so any useful information would be appreciated! Please help!
Click to expand...
Click to collapse
Idk what your phone's actual issue is, but you should probably not have restored efs from previous phone.
At this point, I would probably Odin back to latest stock firmware, to see if the phone will boot and recognize sim card. If so, I would go from there, flash latest official TWRP, format data, and either restore the backup sans modem and efs, or try a different ROM.
DO NOT INSTALL TWRP APP
Also, try to do things in small traceable steps to make it easier to see what is causing your problem.
Eg:
Flash just the bare ROM, nothing else, no Magisk, no hacky crap, just the ROM. Test it.
If everything is satisfactory, then try the next step and test again, working your way up to your desired ROM/kernel/Magisk/apps solution that makes you happy.
For maximum stability it's always preferable to format data (Advanced wipe>format>type yes) when flashing a ROM to ensure a clean slate for everything.
Also, try not too let your phone get too hot with lots of flashing. I've seen good phones do odd stuff when overheated.
That's all the advice I can think of right now, how it is some help to you.
Good luck! :good:

you should probably not have restored efs from previous phone.
Click to expand...
Click to collapse
Yeah, I assume that was the stupidest thing, but an online guide suggested it's ok to restore from another phone's NAND backup as long as it's the same model, so I thought it was safe.
At this point, I would probably Odin back to latest stock firmware, to see if the phone will boot and recognize sim card.
Click to expand...
Click to collapse
My phone works fine with /e/ ROM as before - SIM, Wi-Fi, Bluetooth and all, there is just a constant pop-up saying that the Bluetooth app has crashed interfering with everything I do that wasn't present before the stupid restore to stock.
If so, I would go from there, flash latest official TWRP, format data, and either restore the backup sans modem and efs, or try a different ROM.
Click to expand...
Click to collapse
Did all this except trying a different ROM, because it wasn't producing the Bluetooth app has crashed problem before restoring to stock, so I assumed it's not a ROM problem. The digest problem was present also in Havoc ROM.
DO NOT INSTALL TWRP APP
Click to expand...
Click to collapse
Why? Is this a general issue or just a problem in my case? Anyway I have disabled the option before restarting to system.
Also, try to do things in small traceable steps to make it easier to see what is causing your problem. Eg: Flash just the bare ROM, nothing else, no Magisk, no hacky crap, just the ROM. Test it.
Click to expand...
Click to collapse
Yeah, I was doing the things one step at a time, my message is just a condensed resume of all the steps I did to make it shorter. I stopped adding things once I was unable to flash the kernel, camera mod and Magisk modules - I didn't just add everything I was trying to understand if the problem was just with kernel or my phone wouldn't flash also some other zips.
If everything is satisfactory, then try the next step and test again, working your way up to your desired ROM/kernel/Magisk/apps solution that makes you happy.
Click to expand...
Click to collapse
Yes, yes, that was the plan, but now the bare ROM doesn't want to work anymore without giving me Bluetooth app crashes
For maximum stability it's always preferable to format data (Advanced wipe>format>type yes) when flashing a ROM to ensure a clean slate for everything.
Click to expand...
Click to collapse
I did that before every flash.
Also, try not too let your phone get too hot with lots of flashing. I've seen good phones do odd stuff when overheated.
Click to expand...
Click to collapse
Good to know!
That's all the advice I can think of right now, how it is some help to you. Good luck!
Click to expand...
Click to collapse
Thank you. So now I flashed the latest .tar.md5 file for my model and my CSC through Odin and the phone wouldn't boot to stock ROM (I guess because it had /e/ Pie on it already and the latest stock ROM is just Marshmallow so it's considered downgrading), got stuck at SAMSUNG logo and phone went extremely hot. I pulled out the battery, went in download mode, flashed TWRP, wiped all partitions, formatted data, flashed /e/, booted /e/, the message about Bluetooth app crashing persists, went to TWRP, tried to flash Intelli kernel, got the "digest" error, tried camera mod, got "digest error" again, magisk flashed fine, so flashing works... so what now? I checked inside the .tar.md5 file and there is no efs partition so I guess it wasn't written over by flashing through Odin
Should the phone be able to boot to stock? Is that even necessary - would it fix anything?

ShalaMala said:
My phone works fine with /e/ ROM as before - SIM, Wi-Fi, Bluetooth and all, there is just a constant pop-up saying that the Bluetooth app has crashed interfering with everything I do that wasn't present before the stupid restore to stock.
Click to expand...
Click to collapse
"If so, I would go from there, flash latest official TWRP, format data, and either restore the backup sans modem and efs, or try a different ROM."
A: Did all this except trying a different ROM, because it wasn't producing the Bluetooth app has crashed problem before restoring to stock, so I assumed it's not a ROM problem. The digest problem was present also in Havoc ROM.
Click to expand...
Click to collapse
Maybe try flashing just the baseband with latest modem, etc from haggertk's archive on AFH, here:
https://androidfilehost.com/?w=files&flid=59628
You can flash that without wiping and it only touches the baseband/firmware files, so should not affect anything else
"DO NOT INSTALL TWRP APP"
A: Why? Is this a general issue or just a problem in my case? Anyway I have disabled the option before restarting to system.
Click to expand...
Click to collapse
It's a general issue. The app is bloatware and is known to sometimes cause bootloops see @curiousrom 's post here:
TWRP App Causing Bootloop or Fail To Boot
It's frustrating that TWRP is setup to facilitate easy swiping to install the app
A: Thank you. So now I flashed the latest .tar.md5 file for my model and my CSC through Odin and the phone wouldn't boot to stock ROM (I guess because it had /e/ Pie on it already and the latest stock ROM is just Marshmallow so it's considered downgrading), got stuck at SAMSUNG logo and phone went extremely hot.
Click to expand...
Click to collapse
Unlikely due to /e/ ROM, I have had this happen before. Just pulled battery, hold power button with no battery or charge cable for at least 10 sec to clear remaining charge (I have one phone that will get itself so out of shape that I have to leave it overnight with no battery before it will boot), let it cool, reinstalled battery and try again. Usually it will boot after this.
I pulled out the battery, went in download mode, flashed TWRP, wiped all partitions, formatted data, flashed /e/, booted /e/, the message about Bluetooth app crashing persists, went to TWRP, tried to flash Intelli kernel, got the "digest" error, tried camera mod, got "digest error" again, magisk flashed fine, so flashing works... so what now? I checked inside the .tar.md5 file and there is no efs partition so I guess it wasn't written over by flashing through Odin
Should the phone be able to boot to stock? Is that even necessary - would it fix anything?
Click to expand...
Click to collapse
Flashing stock ROM can sometimes help fix EFS issues, so that is why I suggested that. I also like to see the stock ROM boot with all functions working to make sure the hardware is ok.
I don't assume you haven't done any of the things I suggest. I'm just brainstorming to see if I can help you from my personal experience with my S5s.
Hope you can get yours working:good:

Maybe try flashing just the baseband with latest modem, etc from haggertk's archive on AFH, here:
androidfilehost.com/?w=files&flid=59628
Click to expand...
Click to collapse
I'm reading some instructions: ohthehugemanatee.org/blog/2015/04/04/how-and-why-to-update-the-modem-slash-baseband-firmware-on-a-samsung-phone about how to flash baseband as this is something I've never done before and I'm afraid to mess my device even further... They say "Note that each carrier handles their own updates, so they package their own modem firmwares with slightly different serial numbers. There shouldn’t be any significant difference, but check which one comes from your country and provider".
So I searched for the CSC of the firmware you've linked and it seems to be XXU: samfrew.com/download/GALAXY__S5__/1l88/BTU/G900FXXU1CRH1/G900FOXA1CRH1, which turns out to be a "Multi-CSC for some of the countries and regions (“O” refers to Open)"... is that "some" that bothers me as XXU is not listed under my country's CSC list.
Should I worry? Is it possible to try out if this baseband solves my problems and if it will not work return to the previous version flashing the stock ROM again or am I risking to brick my phone? I didn't find a baseband for my country's csc (SIO) as I will not be receiving any official updates anymore should I change my phone's CSC to XXU first?
(I'm not able to post URL's yet, so they are truncated.)