Hi guys,
I've got a problem. On Tuesday I was updating my apps on Google Play - I've updated some apps and started just to use them. One of them was popular messenger in Poland. Something's went wrong and my smarthphone freezed. I pulled out the battery after few minutes to prepare a 'soft reset', but it stucked on bootloop. I've tried to make a wipe /data, but it couldn't even mount /data, so I decided to change the ROM from networks' one to newest stock one (one file rom). Everything's went good, but it still stucks on bootloop on another boot animation. I've tried also repartitioning it using the stock rom with "totoro_0623.pit" - still the same. Wiping data after flashing didn't give any change.
When the phone was restarting after the last flash, they was written that /data can't be mounted (invalid arguments).
I don't know what should I do right now. Do you have any propositions for me?
Thanks in advance!
you can try with my firmeware
download
http://d-h.st/FhE
unzip the file
put phone into download mode
connect to pc
start odin
put the files in the following places in odin
pda in pda
modem in phone
csc in csc
begin flashing
do not remove the cable untill the phone has fully booted
it will enter stock recovery and flash csc and restart itself so leave cable connected
this firmware is a wipe pack so it should wipe all your partitions
if it fails you can try with the pit file but do not tick the repartition box in odin or you will be in trouble as you need to also include bootloader files for that
marcussmith2626 said:
if it fails you can try with the pit file but do not tick the repartition box in odin or you will be in trouble as you need to also include bootloader files for that
Click to expand...
Click to collapse
Thanks for reply.
Is it recognized as a stock rom? And the second question: what should I do when I have tick on 'repartition'? What changes will be done then? I thought it's just repartitioning and the bootloader is still the same, without any changes.
Ult1me said:
Thanks for reply.
Is it recognized as a stock rom? And the second question: what should I do when I have tick on 'repartition'? What changes will be done then? I thought it's just repartitioning and the bootloader is still the same, without any changes.
Click to expand...
Click to collapse
if you tick repartition it will wipe your boot partition and your phone wont be able to boot which is why you have to put bootloader files in
you dont need to repartition - in all the times iv flashed stock roms iv never had to do it
That link is for stock room firmware XXMI1 on baseband XXMC2 - its european firmware but will work on any gt-s5360 to get it working
You can always change to another baseband if you find you have no network by flashing a stock rom from your region
Sorry but I didn't have enough time to prepare it in this week. As I saw, I probably need also the bootloader files. Can somebody point me which one will be good? And another question: after changing bootloader the counter on downloading mode will be incremented?
Ult1me said:
Thanks for reply.
Is it recognized as a stock rom? And the second question: what should I do when I have tick on 'repartition'? What changes will be done then? I thought it's just repartitioning and the bootloader is still the same, without any changes.
Click to expand...
Click to collapse
This is a firmware and bootloader provided, I had same problem 4 days ago and this helped me alot
Sent from my GT-S5360 using xda premium
Somebody who tried to repair this phone ticked 're-partition' in my case, but this pack has helped me a lot. Thank you guys, you're amazing.
2 days ago i flashed twrp on my pure stock note 4, i did backup my rom including EFS using twrp and then flash kyubi rom with nameless kernel, it all went well. just now i wipe data ,system, cache on twrp and restore my backup stock rom and it went well too...and then i try to flash stock rom using odin so i can get back the stock recovery mode for OTA update when MM releases.. the flashing was a sucess and phone booted but my data inside werent wipe.
so i went to recovery mode and saw this dm-verity verification failed on the bottom i proceed to wipe data and reboot my phone, its all working now no problems except i cant reset my phone with the setting inside it will just bring me to recovey mode and stay there with that message.
now i did some research, some saying will bootloop and stuffs but mine is all ok no problem except i cant reset it inside the settings..
anyone can help me get rid of that message/problem?
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
got the same problem. Then I went to a local store. They helped me. Here are steps
1. Pull out your battery, check your serial number (S/N:....)
2. Download smart switch, enter emergency software recovery..... Enter your serial number
3. Turn off your phone. Enter download mode or sth ( I don't remember it clearly. just power + vol down or up. just try it)
4. Smart switch will recognize your phone. Choose a firmware to download. then wait
5. Enjoy stock firmware
Use kies3 reinstall drivers, then use emergency recovery in kies to reinstall your current firmware or opt to update to latest or most recent release or version then follow kies instructions
rooted s5 smg900r4
Hello everyone
I have found a way to fix dm-verity and DRK issues and it works like official, meaning no errors in stock recovery and OTA works with Official firmware, the problem is related to corrupted/deleted 3 files on /efs partition. I have tested it on SM-N910C so I guess it works on other Exynos variants, perhaps even on snapdragon if the partition layout is similar? Kies won't restore DRK or dm-verity check because it doesn't write to EFS. I can fix yours if someone is interested via Team Viewer, you will need the following:
1. PM contact me for Skype ID
2. Stock rom, rooted (any root method)
3. Adb debugging enabled and drivers installed (Kies or SmartSwitch)
After repair you can enter your stock recovery and confirm there is no DRK/dm-verity red letters error.
Regards,
magix01
please guide us the proceedure here .. i have a phone with same problem & i have to update it to MM ...
dork997 said:
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
Click to expand...
Click to collapse
Mine still says fail. but it also says "need to check drk first" could anyone possibly help me im stuck.the phone loads up and everything. but when i try to root or anything or flash any other firmware than n910pvpu5dqi5 it fails about 4 seconds in to flashing on odin. ive downloaded every possible firmware specific to the SM-N910P but only one worked.
im a big noob with the note 4 this is my first luckily its not my daily phone yet. im very familiar with the note 3 n900t but im finding they are very different. any advice would be appreciated!
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Manish_k said:
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Click to expand...
Click to collapse
If you just unlocked your bootloader and thats it, your rom should still be the stock one.
Hi all,
I bricked my phone installing nougat and after i formatted all. Now my phone can start in download mode only or loops on Boot logo.
Ca anyone help me to fix it? How can I find the right OEM firmware?
Thanks.
Hi. What do you mean by formatted all? If you formatted system your os is gone and phone won't boot.
Check updato for firmware fownload and flash with Odin.
Skickat från min Honor5X
From Recovery i clicked on all wipe functions. My phone is empty now. I flashed a PIT file and a bootloader but I got error flashing CSC and other.
Can you help me to find a full backup to restart my phone?
Originally it was brand tim but It'n not important for me.
creativesound said:
From Recovery i clicked on all wipe functions. My phone is empty now. I flashed a PIT file and a bootloader but I got error flashing CSC and other.
Can you help me to find a full backup to restart my phone?
Originally it was brand tim but It'n not important for me.
Click to expand...
Click to collapse
You got twrp recovery? If you do, you probably wiped system partition too.
You don't need to flash pit, bootloader etc. You can just flash any custom rom to get it booted again.
Otherwise you'll have to download firmware to flash in odin. You probably need one starting with FXXU3 if you was updated to latest MM version, or N.
I wiped all. Can you guide me to download right file?
Hello everybody,
I got a Samsung Galaxy S7 Edge (SM-G935F) DBT version and flashed a Custom ROM (Firmware? idk the difference).
I did that like this: youtube.com/watch?v=_1ofpLHMVvA
Unfortunately there were a few problems there, like the camera is awful now (Bad quality and other camera apps didnt made it better).
So now I want back my Stock ROM. (Yes, Unfortunately I didnt made a Backup)
But I cant get it back, neither with TWRP or with Odin.
At Odin its stops at system.img and fails than and at TWRP I guess I used the wrong Rom because is said Zip file is corrupt!.
The following Stock ROM did I use for Odin and TWRP: updato.com/firmware-archive-select-model?record=2A12F0CE03CD11E7963AFA163EE8F90B
At Odin I unziped it and added it the right way: (BL, AL, CP and CSC).
At TWRP I didnt unziped it and used it like it is.
I hope you can help me there.
I have already made the following:
Changed USB Port
Changed USB cabel
Used Smart Switch
And yes, I can still install custom roms like LineageOS and Resurrection easily via TWRP.
Greetings, Darkatzu.
bump
Darkatzu said:
bump
Click to expand...
Click to collapse
Which procedure you followed to root and install custom rom?
Sent from my S7 Edge using XDA Labs
shah22 said:
Which procedure you followed to root and install custom rom?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Is that important? I dont think so...
Darkatzu said:
Is that important? I dont think so...
Click to expand...
Click to collapse
It is, because you will need no verity opt encrypt to flash too alongside official stock rom in order to use stock rom if you rooted by system modification method, with oreo 8.0 I think no verity zip is not working, so you need to flash latest nougat for your country/region alongside twrp , no verity zip and super su, you can download latest stock firmware for your region from samfirm application or updato, also download odin version 3.13.1, latest twrp recovery, super su and no verity opt encrypt from here on xda forums, first check and enable oem unlock, flash stock rom and then flash twrp through odin, then boot in twrp recovery and flash no verity and super su zips, to get detailed info on above steps search the forums. AND PLEASE TELL WHATS ASKED IF YOU WANT TO GET HELPED.
!! NOTE : IF YOU ROOTED FIRST TIME BY SYSTEM MODIFICATION METHOD, AND THEN INSTALLED CUSTOM ROM, THEN FLASHING STOCK ROM BACK WILL PUT YOU ON A DM VERITY ERROR. ALWAYS REMEMBER TO ENABLE OEM UNLOCK IN DEVELOPER OPTIONS BEFORE DOING ANYTHING!
HAVING OEM UNLOCK DISABLED AND THEN ROOTING VIA SYSTEM MODIFICATION METHOD, AND THEN FLASHING STOCK ROM WILL PUT YOU IN A HARD BRICK SITUATION WITH BOTH DM VERITY ERROR AND CUSTOM BINARY BLOCKED ERROR !!
As far as I know the above situation has no solution if you get into this mess and only a memory swap on board or some box can fix this. I know many users here on xda are stuck on this situation. Some users said they fixed this by using nand erase all and re partition using pit file options during flashing in odin, but I really doubt enabling these options will solve this if not making problems worse. Anyone is welcomed to correct me if the above situation has any solution. BUT THAT IS WHY SYSTEMLESS ROOT IS THERE TO AVOID ALL THIS...
Sent from my S7 Edge using XDA Labs
shah22 said:
It is, because you will need no verity opt encrypt to flash too alongside official stock rom in order to use stock rom if you rooted by system modification method, with oreo 8.0 I think no verity zip is not working, so you need to flash latest nougat for your country/region alongside twrp , no verity zip and super su, you can download latest stock firmware for your region from samfirm application or updato, also download odin version 3.13.1, latest twrp recovery, super su and no verity opt encrypt from here on xda forums, first check and enable oem unlock, flash stock rom and then flash twrp through odin, then boot in twrp recovery and flash no verity and super su zips, to get detailed info on above steps search the forums. AND PLEASE TELL WHATS ASKED IF YOU WANT TO GET HELPED.
!! NOTE : IF YOU ROOTED FIRST TIME BY SYSTEM MODIFICATION METHOD, AND THEN INSTALLED CUSTOM ROM, THEN FLASHING STOCK ROM BACK WILL PUT YOU ON A DM VERITY ERROR. ALWAYS REMEMBER TO ENABLE OEM UNLOCK IN DEVELOPER OPTIONS BEFORE DOING ANYTHING!
HAVING OEM UNLOCK DISABLED AND THEN ROOTING VIA SYSTEM MODIFICATION METHOD, AND THEN FLASHING STOCK ROM WILL PUT YOU IN A HARD BRICK SITUATION WITH BOTH DM VERITY ERROR AND CUSTOM BINARY BLOCKED ERROR !!
As far as I know the above situation has no solution if you get into this mess and only a memory swap on board or some box can fix this. I know many users here on xda are stuck on this situation. Some users said they fixed this by using nand erase all and re partition using pit file options during flashing in odin, but I really doubt enabling these options will solve this if not making problems worse. Anyone is welcomed to correct me if the above situation has any solution. BUT THAT IS WHY SYSTEMLESS ROOT IS THERE TO AVOID ALL THIS...
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I showed a Video Tutorial how I did that.
The reason why I did that, is for me: Not important.
And yes, I did OEM unlock.
shah22 said:
so you need to flash latest nougat for your country/region alongside twrp
Click to expand...
Click to collapse
So far so good.
shah22 said:
you can download latest stock firmware for your region from samfirm application or updato
Click to expand...
Click to collapse
As I did. (both)
shah22 said:
also download odin version 3.13.1, latest twrp recovery
Click to expand...
Click to collapse
Already done.
shah22 said:
super su and no verity opt encrypt from here on xda forums
Click to expand...
Click to collapse
Ok I didnt done that, but now I got I did.
shah22 said:
first check and enable oem unlock
Click to expand...
Click to collapse
Done.
shah22 said:
flash stock rom
Click to expand...
Click to collapse
Aaaand failed as I described already.
Darkatzu said:
I showed a Video Tutorial how I did that.
The reason why I did that, is for me: Not important.
And yes, I did OEM unlock.
So far so good.
As I did. (both)
Already done.
Ok I didnt done that, but now I got I did.
Done.
Aaaand failed as I described already.
Click to expand...
Click to collapse
Maybe you are using an older bootloader ? Can't say for sure whats causing it, the method you used above I think required system modifications, but you are using a march 2017 stock rom, so it looks updato don't has V2 bootloader firmwares for DBT, problems may happen when flashing an older bootloader on a newer one, it could also be your pc or other hardware problem, but in case try again and download samfirm from here : https://forum.xda-developers.com/attachment.php?attachmentid=3803841
Enter DBT as your region and model SM-G935F , it will download the latest stock available, be sure option for auto decrypt, check crc32 and binary nature are ticked.
After that check oem unlock and usb debugging is enabled and follow the steps :
1. Put phone in download mode, use original usb cable, and make sure pc usb port is working correctly. Also phone must be charged above 50%.
2. Download odin 3.13.1 from here https://forum.xda-developers.com/attachment.php?attachmentid=4431597&d=1519662712
Latest twrp available https://eu.dl.twrp.me/hero2lte/twrp-3.2.1-1-hero2lte.img.tar.html
Latest no verity opt encrypt https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Latest stable super su https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
3. Put phone in download mode, extract the firmware downloaded above from samfirm tool and put the respective files in their boxes, use CSC and NOT HOME_CSC. Make sure no option other than F.reset time is ticked in odin options. Begin the flash procedure. After it is completed, don't reboot and place twrp zip downloaded from above in the AP tab of odin. After it is completed, stay in download mode and hold power+home+vol down to reboot from download mode and immediately switch to vol up button to boot in twrp recovery menu.
4. In twrp recovery menu, you need to swipe for system modifications or tick read only ( if you previously allowed for system modifications then you can do it again it doesn't matter, but if you previously didn't swipe for system modifications then tick read only and download systemless zip from https://forum.xda-developers.com/s7-edge/development/samsung-systemless-devbase-encryption-t3517178 )
I will recommend this as you won't need to flash dm verity.
5. Now, go to wipe> format data in twrp recovery, after its done, flash super su and system less zip through twrp to get system less root if you don't want to get dm verity error hassle when flashing stock roms OR flash super su and no verity opt encrypt if you already have allowed system modifications. After that reboot. It may take sometime.
Also to note if you never allowed system modifications before in twrp, and you don't want to root either, then you can safely flash stock without flashing twrp or going through further steps.
This is what I could best explain according to my limited knowledge, if you still fail to flash stock in odin, then I am not sure it may be your pc or other hardware problem and you may need a repair box, try checking on another pc or some expert user to help. Good Luck.
These steps are only for installing stock rom back on previously rooted S7 edge devices using custom roms and for rooting a stock rom.. and only applies to SM-G935F
Sent from my S7 Edge using XDA Labs
shah22 said:
Maybe you are using an older bootloader ? Can't say for sure whats causing it, the method you used above I think required system modifications, but you are using a march 2017 stock rom, so it looks updato don't has V2 bootloader firmwares for DBT, problems may happen when flashing an older bootloader on a newer one, it could also be your pc or other hardware problem, but in case try again and download samfirm from here : https://forum.xda-developers.com/attachment.php?attachmentid=3803841
Enter DBT as your region and model SM-G935F , it will download the latest stock available, be sure option for auto decrypt, check crc32 and binary nature are ticked.
After that check oem unlock and usb debugging is enabled and follow the steps :
1. Put phone in download mode, use original usb cable, and make sure pc usb port is working correctly. Also phone must be charged above 50%.
2. Download odin 3.13.1 from here https://forum.xda-developers.com/attachment.php?attachmentid=4431597&d=1519662712
Latest twrp available https://eu.dl.twrp.me/hero2lte/twrp-3.2.1-1-hero2lte.img.tar.html
Latest no verity opt encrypt https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Latest stable super su https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
3. Put phone in download mode, extract the firmware downloaded above from samfirm tool and put the respective files in their boxes, use CSC and NOT HOME_CSC. Make sure no option other than F.reset time is ticked in odin options. Begin the flash procedure. After it is completed, don't reboot and place twrp zip downloaded from above in the AP tab of odin. After it is completed, stay in download mode and hold power+home+vol down to reboot from download mode and immediately switch to vol up button to boot in twrp recovery menu.
4. In twrp recovery menu, you need to swipe for system modifications or tick read only ( if you previously allowed for system modifications then you can do it again it doesn't matter, but if you previously didn't swipe for system modifications then tick read only and download systemless zip from https://forum.xda-developers.com/s7-edge/development/samsung-systemless-devbase-encryption-t3517178 )
I will recommend this as you won't need to flash dm verity.
5. Now, go to wipe> format data in twrp recovery, after its done, flash super su and system less zip through twrp to get system less root if you don't want to get dm verity error hassle when flashing stock roms OR flash super su and no verity opt encrypt if you already have allowed system modifications. After that reboot. It may take sometime.
Also to note if you never allowed system modifications before in twrp, and you don't want to root either, then you can safely flash stock without flashing twrp or going through further steps.
This is what I could best explain according to my limited knowledge, if you still fail to flash stock in odin, then I am not sure it may be your pc or other hardware problem and you may need a repair box, try checking on another pc or some expert user to help. Good Luck.
These steps are only for installing stock rom back on previously rooted S7 edge devices using custom roms and for rooting a stock rom.. and only applies to SM-G935F
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
As I already said: As I did. (both)
I already tried with samfire.
Same error.
Sorry I couldn't be much help. Does it always stucks in odin at system.img? Looks like its a hardware problem in your pc/usb ports or phone's usb jack. Try getting your phone checked by a repairer, flashing from another pc or changing usb cable. Also try running odin as an admin or try with an older odin version. Good Luck
Sent from my S7 Edge using XDA Labs
shah22 said:
Sorry I couldn't be much help. Does it always stucks in odin at system.img? Looks like its a hardware problem in your pc/usb ports or phone's usb jack. Try getting your phone checked by a repairer, flashing from another pc or changing usb cable. Also try running odin as an admin or try with an older odin version. Good Luck
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Yes it suck always at system.img!
And I can easily flash custom roms via. TWRP.
And I can flash TWRP via Odin without any errors.
Do u even read my post?
Changed USB cabel
Click to expand...
Click to collapse
And yes, I changed PC 2 and yes tryed other versions of Odin LIKE where AP is named as PDA.
Strange thing if you could flash recovery but not the stock rom, looks like you need to get it checked by a tech. But as a last resort did you tried using pit file and repartition ticked? To get the pit file extract the CSC file and you will find .pit file there, open pit tab in latest odin and select that pit file, then tick repartition box and proceed to flash with all other files selected in their respective boxes. If its still the same then I guess I can be of no more help. Cheers !
!! Warning : Using pit file is never recommended and it could brick your phone permanently if there is any power outage/usb disconnection during flashing with pit, it is used to correct file system partitions if they are changed/corrupted. Its better to outweigh benefits with potential danger. Also a pit file will erase all partitions first, then write flash data from beginning and if you again stuck at system.img when using pit file, you will be left with a permanent brick. So I will recommend to get it checked by a tech if you want stock rom that bad and don't do any risky thing with your pricey phone
Sent from my S7 Edge using XDA Labs
shah22 said:
Strange thing if you could flash recovery but not the stock rom, looks like you need to get it checked by a tech. But as a last resort did you tried using pit file and repartition ticked? To get the pit file extract the CSC file and you will find .pit file there, open pit tab in latest odin and select that pit file, then tick repartition box and proceed to flash with all other files selected in their respective boxes. If its still the same then I guess I can be of no more help. Cheers !
!! Warning : Using pit file is never recommended and it could brick your phone permanently if there is any power outage/usb disconnection during flashing with pit, it is used to correct file system partitions if they are changed/corrupted. Its better to outweigh benefits with potential danger. Also a pit file will erase all partitions first, then write flash data from beginning and if you again stuck at system.img when using pit file, you will be left with a permanent brick. So I will recommend to get it checked by a tech if you want stock rom that bad and don't do any risky thing with your pricey phone
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
A tech is 2 expensive for me.
And yes, I already did it with pit file and the whole CSC file.
#push
#push
#push
#push
Darkatzu said:
#push
Click to expand...
Click to collapse
try with chimeratool, it worked for me, l use a free license to download the firm from server and install it
#push
shah22 said:
It is, because you will need no verity opt encrypt to flash too alongside official stock rom in order to use stock rom if you rooted by system modification method, with oreo 8.0 I think no verity zip is not working, so you need to flash latest nougat for your country/region alongside twrp , no verity zip and super su, you can download latest stock firmware for your region from samfirm application or updato, also download odin version 3.13.1, latest twrp recovery, super su and no verity opt encrypt from here on xda forums, first check and enable oem unlock, flash stock rom and then flash twrp through odin, then boot in twrp recovery and flash no verity and super su zips, to get detailed info on above steps search the forums. AND PLEASE TELL WHATS ASKED IF YOU WANT TO GET HELPED.
!! NOTE : IF YOU ROOTED FIRST TIME BY SYSTEM MODIFICATION METHOD, AND THEN INSTALLED CUSTOM ROM, THEN FLASHING STOCK ROM BACK WILL PUT YOU ON A DM VERITY ERROR. ALWAYS REMEMBER TO ENABLE OEM UNLOCK IN DEVELOPER OPTIONS BEFORE DOING ANYTHING!
HAVING OEM UNLOCK DISABLED AND THEN ROOTING VIA SYSTEM MODIFICATION METHOD, AND THEN FLASHING STOCK ROM WILL PUT YOU IN A HARD BRICK SITUATION WITH BOTH DM VERITY ERROR AND CUSTOM BINARY BLOCKED ERROR !!
As far as I know the above situation has no solution if you get into this mess and only a memory swap on board or some box can fix this. I know many users here on xda are stuck on this situation. Some users said they fixed this by using nand erase all and re partition using pit file options during flashing in odin, but I really doubt enabling these options will solve this if not making problems worse. Anyone is welcomed to correct me if the above situation has any solution. BUT THAT IS WHY SYSTEMLESS ROOT IS THERE TO AVOID ALL THIS...
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
hi, i used this thread to root my regular s7 from sprint, am i going to be able to just flash the latest firmware back to stock and be good to go or am i hosed?
thanks
hikouka71 said:
hi, i used this thread to root my regular s7 from sprint, am i going to be able to just flash the latest firmware back to stock and be good to go or am i hosed?
thanks
Click to expand...
Click to collapse
No, i don't think so as you already flashed engineering kernel, i won't recommend but if you already tried, do post your results ..
Sent from my S7 Edge using XDA Labs
I flashed the combination of binary U2 to restore my i Mei and drk error but it shows modem crash in the binary mode and cp crash mode.
I hope someone can give me a solution that's useful and it's okay for me to pay by PayPal after it has been fixed.
The following is the message I sent to cubz but he doesn't seem to be free to active these days so I hope anyone else can help me.
The letter :
{{{{Hi, I've seen many posts in the xda and many people refer the solutions and fix advice to your name on comment so I think you will be the only one who can help with my issue.
Firstly, I had my S7 edge flashed with many roms before and flashed with odin ( with sim card always, not knowing if this is a major problem), but after once I did after using the encryption on the S7 edge with the lineage OS ( the 8.1.0 one in Feburary), I tried to flash with other rom without decrypted it and flashed fail. ( roms are all android 7.0 and 7.1.2)
Since then, I tried to flash other rom (7.0 like superman rom or rom from SAC) but still losing cellunar signal. then I tried to flash the original android 6.0 official firmware through odin but it failed on the step which shows DRK error on the samsung official 6.0 recovery.
After reading your post on how to fix DRK error, I tried the method but maybe because of I don't really know the steps or how to restore on the binary factory firmware, it boots up but still lose of IMEI and cellunar signal.
After the android 8.0 is released officially, I flashed the official rom and I tried using the U2 version of bootloader binary factory which you shared, but same problem happens and I also tried the V5.7 devbase rom and same.
Very seldomly the baseband and imei will show as normal and having cellunar signal but not long and after I reboot will gone to unkonwn to the imei and baseband and show as 'no sim card'. ( there was one time that I ticked clear efs on odin then i lost the imei. But after i flashed the binary firmware, imei show unknown in the binary firmware mode but when i flashed back the devbase rom with twrp, the situation of mostly showing unkonwn of baseband and imei happens but very seldomly it will load as normal which they are shown correctly)
*Btw the first flash the U2 binary firmware( Im using the U2 version because my bootloader has been updated to the oreo one), it boots into the screen that shows cp upload or modem upload error? page , then i flash again but with efs clear which was what happened as I mentioned before. ( thats the only time I ticked EFS clear as i can remember)
Dear CuBz90:
I really hope that my s7 edge can be fixed because I have had it for more than two years already and it was the first time that i buy a phone using my own my money but not my parents, I hope you can help me with this issue.
Thank you very much!!!
( its okay if I have to pay( its okay through paypal) after its fixed, but hopefully not too much)}}}}
Cp crash upload exactly same as photo I found in the following link: (please add www by yourself coz it doesnt allow me to post external link as being a new user)
.galaxys-team.fr/viewtopic.php?t=49038
Thank you for patiently read and helping me to find solution for my S7edge (G935F)
help me too
I have the same problem... idk what i can do.................:crying::crying::crying:
it's my pleasure to help you