Related
I got a refurbished Verizon S5 today. It was running the latest Verizon software (PF4?). After using Odin to flash stock tars, the phone's screen now stays off after the first Samsung splash screen. After the normal amount of boot up time, I can hear the normal keyboard sound effects when I tap on the screen but the screen stays off. Sometimes I can get the phone into recovery but most of the time, the phone says "recovery booting..." and then restarts. I can almost always get the phone into download mode. When the phone is plugged into a charger, the grey battery icon shows up and then the phone restarts.
Here's a chronology:
I got the refurbished phone in the mail. I turned it on and checked the cid. 11
I used Odin to flash G900VVRU2BPB1...tar.md5. It hung on the red Verizon screen for over 30 minutes so I pulled the battery and let it boot again. Still hung. I used Odin to flash PD1. Went into recovery mode and cleared cache and factory reset. Tried PF4 and PD1. It was around this time that the screen started to go black during and after boot. Tried the debrick image on a SD card. Tried PB1.
My next step was to use Kies to reinstall the firmware but I can't find the S/N. The S/N is not under the battery. The imea does not work as the s/n. I'm downloading adb to see if I can pull the s/n through it.
Any other suggestions or ideas? Is this my first brick? Could this be a hardware issue or did I screw up the firmware/boot image somehow?
Try downloading 7 zip file manager Google it
and the bok 3 firmware from Sammobile.Com
Use 7 zip file manager extract and make a tar out of all the Files individually and flash them individually in odin or heimdall
IT's worth a shot I've had to do this sometimes
[email protected] said:
Try downloading 7 zip file manager Google it
and the bok 3 firmware from Sammobile.Com
Use 7 zip file manager extract and make a tar out of all the Files individually and flash them individually in odin or heimdall
IT's worth a shot I've had to do this sometimes
Click to expand...
Click to collapse
Thanks for the suggestions. I've downloaded BOK3 and I have created the individual tar files.
I haven't flashed individual files before. Does order matter? Do certain files get flashed in BL instead of AP?
For example,
BL: aboot, boot
AP: everything else?
It looks like my phone is from one of the earlier manufacturing runs. Could it have been a hardware issue? Google showed some people having the same problem with the screen turning off. Do you think my warranty is void because I've flashed a stock rom?
Boot into Odin and look at the number s1 t1 etc if any are two you warranty is void
---------- Post added at 01:23 AM ---------- Previous post was at 01:22 AM ----------
No order doesn't matter
I was about to sell my rooted Note 4, and I did a "reset phone" in the settings menu to wipe the data out , so I can sell it. When the phone turned back I saw on the top left a blue "recovery mode" message and the next is my phone black, and on the middle of the screen appear every 5-8 sec a green android logo with "Installing System update" but just for a second, and goes back to black.
And again, and again...
What a hell happened?I am stuck.. I tried to take the battery out , waited and put it back, than I was holding the volume up+home+power on bottoms to get a recovery mode menu, but it does the same "flashing" screen thing.. Please help me I have a buyer for this phone , really need to fix it!
atti_mac said:
I was about to sell my rooted Note 4, and I did a "reset phone" in the settings menu to wipe the data out , so I can sell it. When the phone turned back I saw on the top left a blue "recovery mode" message and the next is my phone black, and on the middle of the screen appear every 5-8 sec a green android logo with "Installing System update" but just for a second, and goes back to black.
And again, and again...
What a hell happened?I am stuck.. I tried to take the battery out , waited and put it back, than I was holding the volume up+home+power on bottoms to get a recovery mode menu, but it does the same "flashing" screen thing.. Please help me I have a buyer for this phone , really need to fix it!
Click to expand...
Click to collapse
Download firmware for your model from www.sammobiles.com extract firmware file ,take your phone in download mode by pressing volume down+home+power .you will see warning screen then press volume up.download odin tool for pc and samsung usb drivers for note 4 then open odin press Ap in odin and select firmware file and hit start,wait until odin pass .and your device will be good to go.
Trex888 said:
Download firmware for your model from www.sammobiles.com extract firmware file ,take your phone in download mode by pressing volume down+home+power .you will see warning screen then press volume up.download odin tool for pc and samsung usb drivers for note 4 then open odin press Ap in odin and select firmware file and hit start,wait until odin pass .and your device will be good to go.
Click to expand...
Click to collapse
The sammobiles website down for maintenence this weekend , great.....
atti_mac said:
The sammobiles website down for maintenence this weekend , great.....
Click to expand...
Click to collapse
Tell me your model and I'll provide you a link to download firmware
Trex888 said:
Tell me your model and I'll provide you a link to download firmware
Click to expand...
Click to collapse
SM-N910T
Will be unlocked after this upload?
Thank you so much, can't wait
If Sammobile is down, you can find lots of Samsung firmwares even for SM-N910T on www.updato.com. Hope this helps.
atti_mac said:
SM-N910T
Will be unlocked after this upload?
Thank you so much, can't wait
Click to expand...
Click to collapse
To be honest i donno about unlocking but here is the link to download firmware
https://www.androidfilehost.com/?fid=24665509702140550
Trex888 said:
To be honest i donno about unlocking but here is the link to download firmware
https://www.androidfilehost.com/?fid=24665509702140550
Click to expand...
Click to collapse
I downloaded from there , opened a zip file copied to a folder. Took the phone in download mode, Opened Odin, clicked on AP and got the file to point ( not a zip file anymore) and hit start.
My phone shows downloading, and like a line started from the left (light blue , but only very short, and doesn't move anymore.
The pc's latest log shows ID:0/003> NON-HLOS.bin
So is it stopped ? the phone said don't turn off target, i don't want to brick it so what to do?
I had no choice i unplug it, and took out the battery, still not brick I started all over again, and now the latest log is : boot.img but the line still not moving...
binary size shows : 3793.1 mb
Update , 2nd time it was moving further.. passed boot, recovery.img, latest log : system.img.ext4. the blue line moved 1/2" and it is stopped again. I don't know what to do...
I am using Odin 3 V3.12
Try odin 3.10 and use pit file with firmware it will repartation your device and hopefully it ahould fix here is the link for pit file
https://mega.nz/#!yE0QkRgR!8DvGvAauRkb-2xmtH_3ZluoYwCvqNaaSOnXMLYB_CAI
Select AP for firmware and PIT for pit file and hit start
Trex888 said:
Try odin 3.10 and use pit file with firmware it will repartation your device and hopefully it ahould fix here is the link for pit file
https://mega.nz/#!yE0QkRgR!8DvGvAauRkb-2xmtH_3ZluoYwCvqNaaSOnXMLYB_CAI
Select AP for firmware and PIT for pit file and hit start
Click to expand...
Click to collapse
Same thing, is it possible the md5 file is not the right one?
Update, I downloaded a different file from the www.updato.com. website , and it is already passed that point when was stuck before. Cross fingers.
atti_mac said:
Same thing, is it possible the md5 file is not the right one?
Update, I downloaded a different file from that other website you guys mentioned, and it is already passed that point when was stuck before. Cross fingers.
Click to expand...
Click to collapse
No the firmware file is correct qnd i have tested it. What is exatly happening while you flash firmware?
Ok, i used that 2nd file, and was everything perfect! I got a message on Odin : "PASS" the phone turned on, passed a Samsung logo, the T-Mobile screen turned on, and the T mobile song, and stuck on that screen....
this is a file I used a second time , and I stuck now at boot by the T-Mobile logo
N910TUVU2DOK2_N910TTMB2DOK2_N910TUVU2DOK2_HOME.tar.md5
and this file was the one stuck always at the beginning :
N910TUVS2EPG2_N910TTMB2EPG2_N910TUVS2EPG2_HOME.tarmd5
just a note, my Note 4 was rooted and It wasn't a latest firmware , actually probably like 8 months old or at least 6 month old firmware on it.
WORKING!! 100% Working. I just took out a battery , and was waiting a bit, turned it back and working! Thank You guys!!
you shoud have clear cache and data through recovery after that successful flash..
but you didn't
atti_mac said:
Ok, i used that 2nd file, and was everything perfect! I got a message on Odin : "PASS" the phone turned on, passed a Samsung logo, the T-Mobile screen turned on, and the T mobile song, and stuck on that screen....
this is a file I used a second time , and I stuck now at boot by the T-Mobile logo
N910TUVU2DOK2_N910TTMB2DOK2_N910TUVU2DOK2_HOME.tar.md5
and this file was the one stuck always at the beginning :
N910TUVS2EPG2_N910TTMB2EPG2_N910TUVS2EPG2_HOME.tarmd5
just a note, my Note 4 was rooted and It wasn't a latest firmware , actually probably like 8 months old or at least 6 month old firmware on it.
WORKING!! 100% Working. I just took out a battery , and was waiting a bit, turned it back and working! Thank You guys!!
Click to expand...
Click to collapse
Wipr cache and make factory reset in recovery to get clean system firmware.
Hello guys,
A friend of mine gave me his S6EDGE+ because it didnt boot anymore after he woke up. The night before that he installed an update but the phone worked fine after that.
The phone showed this message: http://imgur.com/a/cwLyM
I thought that it was easily fixed by flashing original 7.0 firmware but as you can guess i was wrong... It keeps rebooting right after the "Samsung Galaxy S6 Edge+" screen
So i tried to flash original 6.0.1 firmware but the same result
After that i flashed 7.0 again and after that twrp 7.0 but it never booted into twrp
So i flashed android 6.0.1 and the newest twrp for 6.0.1 but it still didnt booted into recovery and i am not able to boot in recovery.
After that i tried some older versions of twrp for 6.0.1 and it sometimes gave me the error: Recovery is not seandroid enforcing. I tried the same with 7.0 and older twrp versions, same results.
I also tried to flash 5.1.1 but i couldnt flash it.
What i also tried is to flash 7.0 bootloaders and after that 7.0 firwmare and the same for 6.0.1
I'm really desperate and dont know what to do anymore..
Current status: bootloop
I can enter download mode: http://imgur.com/a/XiS6Z
When you say you flashed original firmware, did you use odin to do it? Did you use the firmware from sammobile?
Apologies if it's shows in the pictures, but they aren't showing up on my phone.
1. how about if you try to reflash twrp, full wipe and install a rom?
2. Try fix it with Smart Switch with emergency frimware recovery / emergency device recovery. ?
kdogguk said:
When you say you flashed original firmware, did you use odin to do it? Did you use the firmware from sammobile?
Apologies if it's shows in the pictures, but they aren't showing up on my phone.
Click to expand...
Click to collapse
i can see that the images aren't working, ill fix that in a sec.
Yes i used odin and downloaded everything from sammobile because ive actualy paid them for de downloadspeed
justanpotato said:
1. how about if you try to reflash twrp, full wipe and install a rom?
2. Try fix it with Smart Switch with emergency frimware recovery / emergency device recovery. ?
Click to expand...
Click to collapse
ive flashed several versions of twrp but it never boots in recovery or i get the message recovery is not seandroid enforcing.
I also tried the Smart Switch method but without succes
no, u need learn some things about Binary Vercion, ima sure u have a B3 in this moments, so , download any firmware with Binary 3, if need more infor about that, check here http://forum.gsmhosting.com/vbb/f68...combination-compatibility-w-o-errors-2189001/
ruubs said:
ive flashed several versions of twrp but it never boots in recovery or i get the message recovery is not seandroid enforcing.
I also tried the Smart Switch method but without succes
Click to expand...
Click to collapse
You've never stated the results of your stock firmware flashing, using Odin. This is key, this tells you whether the firmware was flashed correctly or not.. If you picked the wrong stock firmware to flash, Odin will show it "Failed."
If your buddy just updated firmware, then it's likely he's on the newest one, but check in SamMobile to verify if it's accurate. If shows the most current firmware was updated in January or something then he might not be on the most current one, as this shows that he's behind on updating his phone, so it's uncertain which it last updated to.
If I were you, I'd verify first whether the Odin flash passed or not, prior to attempting any custom flashing.. After Odins finished flashing in the upper right corner will either show "Pass" or "Fail," it needs to show "Pass" before you can proceed to do anything else, as this confirm whether the stock firmware flashed correctly or not.
If it doesn't Pass, you have flashed the wrong firmware. Might be good to verify with your buddy, which carrier he had originally. If you indeed have a Samsung S6 Edge+, with the larger 5.7 inch screen, the model numbers begin as so, "SM-G928x" with difference being the "x" at the end, which coincides with whichever carrier it's on, (e.g. "A" for AT&T, "T" for T-Mobile" - U.S. carriers).
It wouldn't be a bad idea to confirm whether you're using the most up to date version of Odin, either. Don't remember what that is but a quick Google search under this topic would do it.
Just for shyts and giggles, you did verify that your PC recognizes the phone, right? And that it lists under "Device Manager" correctly, as well as Odin recognizing it after you plugged it in?
If it does "Pass," it should reboot by itself into the stock firmware since prior to flashing you selected "autoreboot" and "reset time" if it doesn't reboot correctly or gets stuck on the splash screen, unplug it from the PC and manually boot it into stock recovery. Do this by first pressing the following buttons at the same time and holding them till the phone powers off, power button, home button, volume up and volume down.. After it powers off, push and hold, power button, home button and volume up, till the phone boot to stock recovery, amd of course you can let go of the buttons/keys. Then using volume buttons to select factory reset and pressing the power button to confirm the selection. After it factory resets you can then select reboot to system and it should boot normally and you've recovered the phone.
The upper left corner in Odin will show the results of the flash, there shouldn't be a reason for it not booting if it indeed shows "Pass," cuz this confirms firmware flashed correctly, if it shows "Fail" then you flashed the incorrect firmware. You'll need to locate the right one so that Odin shows "Pass," otherwise you wont ever recover your phone, regardless of anything else you find interesting to flash, bootloaders, TWRP, root, ect.. Don't flash anything else till you get the stock firmware flashed correctly. If you're unable to accomplish this then, I'd recommend calling Samsung or your carrier, is it still under warranty? My charging port broke after 2+ years, I have insurance though w/ T-Mobile, called them to see what my options were, was planning on fixing it myself to avoid the $175 insurance deductible, if I made a claim, but as it turns out, since I have insurance, the phones still under warranty and per the CSR, it will continue to hace warranty as long as I pay the $7/month insurance. Thought most warranties are 12 months but I wasn't going to correct her if she was wrong so I went ahead with it and 2 days later new phone came and I sent my broken one back! Old phone has lil scratches on the screen, couple lil dings along the sides, obviously an older phone but now I gotta new one, ita flawless!
It won't to try if this don't work out..
Good luck
Hi - This all started when I was installing a wifi booster on my home network. My stock 935V suddenly rebooted and a black screen with the words at the top left of the screen in blue
Recovery booting
This stayed like that so I left it for two days to fully drain it and then re-charged and I tried to power it up. Same screen - no change. I booted to the download screen and since then have tried the following:
One Nouget flash - errored out saying too old of a version
The 2 newest Oreo versions off sammobile - both do not report a fail, however they hang and nothing proceeds. I wanted to see where they hang and both hang during the CS portion of the install. See screen print attached. I have tried 3 different cables, 2 versions of Odin, 2 computers - all with the same result.
With COVID right now, Verizon is less than eager to help. They say I will have to wait until a service center opens.
View attachment 4989655
Any suggestions from you guys? Thanks in advance,
Signed COVID free Texan
Sullyfamily said:
Hi - This all started when I was installing a wifi booster on my home network. My stock 935V suddenly rebooted and a black screen with the words at the top left of the screen in blue
Recovery booting
This stayed like that so I left it for two days to fully drain it and then re-charged and I tried to power it up. Same screen - no change. I booted to the download screen and since then have tried the following:
One Nouget flash - errored out saying too old of a version
The 2 newest Oreo versions off sammobile - both do not report a fail, however they hang and nothing proceeds. I wanted to see where they hang and both hang during the CS portion of the install. See screen print attached. I have tried 3 different cables, 2 versions of Odin, 2 computers - all with the same result.
With COVID right now, Verizon is less than eager to help. They say I will have to wait until a service center opens.
Any suggestions from you guys? Thanks in advance,
Signed COVID free Texan
Click to expand...
Click to collapse
Hello, what recovery words did you saw ? Also what was the current firmware number of your device if you remember (or see it in recovery mode if you can enter it)
Sent from my S7 Edge using XDA Labs
shah22 said:
Hello, what recovery words did you saw ? Also what was the current firmware number of your device if you remember (or see it in recovery mode if you can enter it)
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Recovery booting. See screen shots. These are the only 4 screens I can reproduce on the S7
View attachment 4991167
Sullyfamily said:
Recovery booting. See screen shots. These are the only 4 screens I can reproduce on the S7
Click to expand...
Click to collapse
Strange, never saw that screen.. any chance you remember firmware number that was installed in your device before this started ?
Sent from my S7 Edge using XDA Labs
shah22 said:
Strange, never saw that screen.. any chance you remember firmware number that was installed in your device before this started ?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
My wife and I have identical phones so I am assuming her's is the same.
R16NW.G935VVRSBCTC1
Sullyfamily said:
My wife and I have identical phones so I am assuming her's is the same.
R16NW.G935VVRSBCTC1
Click to expand...
Click to collapse
Ok thanks. I advise you to download this rom here and flash it in latest odin 3.13.1 , ALSO unzip rom after download and extract the 4 files then put all 4 of them in their respective boxes. And try flashing all 4 at once.
Just to tell you, YOU CANNOT FLASH ANY LOWER FIRMWARE THEN THESE TWO due to BOOTLOADER impossible to downgrade..
First : https://www.sammobile.com/samsung/g...e/SM-G935V/VZW/download/G935VVRSBCTC1/330033/
Second :
https://www.sammobile.com/samsung/g...e/SM-G935V/VZW/download/G935VVRSBCTA1/317274/
(Try both whichever works)
Also this is international s7 edge exynos forum, yours is snapdragon variant , don't follow anything here unless specificly stated that it applies to your variant. Also try asking on s7 edge verizon forum. Good luck.
Sent from my S7 Edge using XDA Labs
shah22 said:
Ok thanks. I advise you to download this rom here and flash it in latest odin 3.13.1 , ALSO unzip rom after download and extract the 4 files then put all 4 of them in their respective boxes. And try flashing all 4 at once.
Just to tell you, YOU CANNOT FLASH ANY LOWER FIRMWARE THEN THESE TWO due to BOOTLOADER impossible to downgrade..
First : https://www.sammobile.com/samsung/g...e/SM-G935V/VZW/download/G935VVRSBCTC1/330033/
Second :
https://www.sammobile.com/samsung/g...e/SM-G935V/VZW/download/G935VVRSBCTA1/317274/
(Try both whichever works)
Also this is international s7 edge exynos forum, yours is snapdragon variant , don't follow anything here unless specificly stated that it applies to your variant. Also try asking on s7 edge verizon forum. Good luck.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Thank you for the suggestions and I'm sorry for posting in the wrong group.
I flashed the CTC1 and it flashed with no errors. The only problem is when it boots now, all that comes up is still the upper left blue writing "Recovery booting". I'm puzzled. What is wrong?
Sullyfamily said:
Thank you for the suggestions and I'm sorry for posting in the wrong group.
I flashed the CTC1 and it flashed with no errors. The only problem is when it boots now, all that comes up is still the upper left blue writing "Recovery booting". I'm puzzled. What is wrong?
Click to expand...
Click to collapse
That recovery booting is your android recovery menu right? Can you try clearing cache and data and then reboot ?
Also what were you trying to do exactly when your phone got in this state ?
Sent from my S7 Edge using XDA Labs
shah22 said:
That recovery booting is your android recovery menu right? Can you try clearing cache and data and then reboot ?
Also what were you trying to do exactly when your phone got in this state ?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Installing the amplifi mesh router app, when connecting to the amplifi mesh router app the phone just turned off. When I tried to restart it, all I saw was the blue recovery booting screen. I tried to do a factory reset and that didn't help so that is where.
As for clearing the cache, it will not boot to recovery (vol up+home+power). When I press these keys, it just boots to the recovery booting screen and then goes dark.
Sullyfamily said:
Installing the amplifi mesh router app, when connecting to the amplifi mesh router app the phone just turned off. When I tried to restart it, all I saw was the blue recovery booting screen. I tried to do a factory reset and that didn't help so that is where.
As for clearing the cache, it will not boot to recovery (vol up+home+power). When I press these keys, it just boots to the recovery booting screen and then goes dark.
Click to expand...
Click to collapse
So it means your phone is in a recovery bootloop even after reflashing with odin .. very strange indeed.. looks like somehow your nv data (efs) got corrupted because any firmware issue would have been solved by a reflash.. or maybe even a hardware issue. I m sorry i ran out of ideas you will need to take it to service centre guys .. good luck.
Edit : here is the combination file for your phone :
https://androidfilehost.com/?fid=4349826312261742312
Extract and flash it using the AP tab of odin (it doesn't require 4 separate files in odin)
Then follow this thread :
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
Do what it said in OP BUT APPLYING THE COMBINATION ROM AND NORMAL ROM I PROVIDED ABOVE. Try both methods. Good luck
Sent from my S7 Edge using XDA Labs
shah22 said:
So it means your phone is in a recovery bootloop even after reflashing with odin .. very strange indeed.. looks like somehow your nv data (efs) got corrupted because any firmware issue would have been solved by a reflash.. or maybe even a hardware issue. I m sorry i ran out of ideas you will need to take it to service centre guys .. good luck.
Edit : here is the combination file for your phone :
https://androidfilehost.com/?fid=4349826312261742312
Extract and flash it using the AP tab of odin (it doesn't require 4 separate files in odin)
Then follow this thread :
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
Do what it said in OP BUT APPLYING THE COMBINATION ROM AND NORMAL ROM I PROVIDED ABOVE. Try both methods. Good luck
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
The combination file loaded without errors and now I can get to the recovery menu. I followed the "How to fix IMEA/DRK issues and re-flashed the CTC1 files. Now when it boots, a different screen comes up (see pic). There is one positive change, I can now get to the recovery menu (see pick). Am I making any progress here?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sullyfamily said:
The combination file loaded without errors and now I can get to the recovery menu. I followed the "How to fix IMEA/DRK issues and re-flashed the CTC1 files. Now when it boots, a different screen comes up (see pic). There is one positive change, I can now get to the recovery menu (see pick). Am I making any progress here?
Click to expand...
Click to collapse
Well this is new.. never saw such a thing tbh .. any efs corruption that could have caused bootloops should have been fixed by combination firmware..
Btw , did you booted into combination firmware after flashing it ? And then enter *#06# to check imei in combination rom and then go in download mode and flash normal ctc1 rom ?
What i understood is you just flashed combination and then gone into download mode to reflash the stock normal rom (you need to boot into combination and check imei there)
If you did boot into combination and it ran fine and your imei was okay then try reflashing the other CTA1 stock rom after booting into combination rom.
If you could not even boot into combination rom and check the diagnostic menu then at this point i don't know more sorry.. looks like a hardware problem
Edit : lol just saw that in recovery it says your phone is G935A but you said its from verizon?
Does download mode says G935V or G935A ?
Also upload some better quality images xd can't read some details on your previous pics..
A G935V phone flashed with g935v rom doesnot boot .. and after flashing the combination rom for a g935v phone says in recovery that its G935A (att model) ..
This doesnt makes sense
Edit : okay it looks like they are using a single att combination rom for all qualcom U.S s7 edge devices (as its said they can be cross-flashed and work for all qualcomm based s7 edge devices) so they provided an ATT combination rom as a verizon one.. but you still need to confirm what it says in download mode ? G935V or G935A?
So i ask my last question again.. were you able to go into combination rom and check settings and imei ?
Sent from my S7 Edge using XDA Labs
shah22 said:
Well this is new.. never saw such a thing tbh .. any efs corruption that could have caused bootloops should have been fixed by combination firmware..
Btw , did you booted into combination firmware after flashing it ? And then enter *#06# to check imei in combination rom and then go in download mode and flash normal ctc1 rom ?
What i understood is you just flashed combination and then gone into download mode to reflash the stock normal rom (you need to boot into combination and check imei there)
If you did boot into combination and it ran fine and your imei was okay then try reflashing the other CTA1 stock rom after booting into combination rom.
If you could not even boot into combination rom and check the diagnostic menu then at this point i don't know more sorry.. looks like a hardware problem
Edit : lol just saw that in recovery it says your phone is G935A but you said its from verizon?
Does download mode says G935V or G935A ?
Also upload some better quality images xd can't read some details on your previous pics..
A G935V phone flashed with g935v rom doesnot boot .. and after flashing the combination rom for a g935v phone says in recovery that its G935A (att model) ..
This doesnt makes sense
Edit : okay it looks like they are using a single att combination rom for all qualcom U.S s7 edge devices (as its said they can be cross-flashed and work for all qualcomm based s7 edge devices) so they provided an ATT combination rom as a verizon one.. but you still need to confirm what it says in download mode ? G935V or G935A?
So i ask my last question again.. were you able to go into combination rom and check settings and imei ?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I apologize, I did not mention that when it boots after the combination file is loaded, it boots to the Samsung logo, then a screen that says factory binary shows up with gears turning. I never see a screen that says "IME" so no opportunity to input #06#. That factory binary screen stays there for about 30 seconds and then this screen shows up - in case you can't read it, it says Unknown error! rdx-init! test_ns : 0xff Wait.... done - In the center of the screen it says - POWER RESET or UNKNOWN UPLOAD MODE
Sullyfamily said:
I apologize, I did not mention that when it boots after the combination file is loaded, it boots to the Samsung logo, then a screen that says factory binary shows up with gears turning. I never see a screen that says "IME" so no opportunity to input #06#. That factory binary screen stays there for about 30 seconds and then this screen shows up - in case you can't read it, it says Unknown error! rdx-init! test_ns : 0xff Wait.... done - In the center of the screen it says - POWER RESET or UNKNOWN UPLOAD MODE
Click to expand...
Click to collapse
Strange.. very strange that even combination rom fails to boot.. okay i need you to flash the U firmware provided here .. see if it gets your phone booting.. :
https://www.sammobile.com/samsung/g...e/SM-G935U/TMK/download/G935UUESBCTA3/320250/
Also can you verify in download mode that your phone model is G935V ?
Edit : since you could access recovery again in combination rom, did you tried factory data reset and clear cache and rebooted ? Try this before flashing the above rom.
Sent from my S7 Edge using XDA Labs
shah22 said:
Strange.. very strange that even combination rom fails to boot.. okay i need you to flash the U firmware provided here .. see if it gets your phone booting.. :
https://www.sammobile.com/samsung/g...e/SM-G935U/TMK/download/G935UUESBCTA3/320250/
Also can you verify in download mode that your phone model is G935V ?
Edit : since you could access recovery again in combination rom, did you tried factory data reset and clear cache and rebooted ? Try this before flashing the above rom.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Verified that the phone is in fact a G935V
I did try to wipe cache and factiry reset - no change
Installed G935U and here is the ODIN fail
Sullyfamily said:
Verified that the phone is in fact a G935V
I did try to wipe cache and factiry reset - no change
Installed G935U and here is the ODIN fail
Click to expand...
Click to collapse
At this point, i can only say its a blocked wall as all possibilities have been explored.. i fear only a service centre can fix this now.. but just a heads up since you will take it to service centre anyway maybe try one last thing..
Use this odin : https://www.androidfilehost.com/?fid=673956719939831735
Then try flashing the 3 normal stock roms i.e ctc1, cta1 and the u firmware one using the following method.
Extract the csc (NOT home_csc) of the rom you currently want to flash using rar utility to a new folder, copy the pit file in it and name it for that rom (e.g ctc1pit , cta1pit, ufirmwareCTA3pit) and remember where you saved it.. do this for all 3 roms .. saving their pit files separately
Using the above odin select bl, cp, ap and normal csc (NOT Home_CSC)
Then under the Options tab *SELECT ONLY NAND Erase + Repartition + F.Reset*
Then under pit tab select the corresponding pit file for the rom you are currently flashing (DON'T select any other rom's pit file while flashing another rom)
Then begin flashing..
Flash all 3 stock roms using this until all 3 fail or someone works..
If odin succeeds to flash any rom without errors by miracle do this :
After odin reports flashed successfully.. you will still be in download mode.. hold volume down+home+power button to force reboot phone and the moment phone screen goes black (starts rebooting) change the keys you are holding to volume up+home+power button. The trick here is to go into recovery menu from download mode directly without booting into phone..
Once in recovery do a factory data reset + clear cache and then reboot..
Tell me how it goes.. and Good Luck !
shah22 said:
At this point, i can only say its a blocked wall as all possibilities have been explored.. i fear only a service centre can fix this now.. but just a heads up since you will take it to service centre anyway maybe try one last thing..
Use this odin : https://www.androidfilehost.com/?fid=673956719939831735
Then try flashing the 3 normal stock roms i.e ctc1, cta1 and the u firmware one using the following method.
Extract the csc (NOT home_csc) of the rom you currently want to flash using rar utility to a new folder, copy the pit file in it and name it for that rom (e.g ctc1pit , cta1pit, ufirmwareCTA3pit) and remember where you saved it.. do this for all 3 roms .. saving their pit files separately
Using the above odin select bl, cp, ap and normal csc (NOT Home_CSC)
Then under the Options tab *SELECT ONLY NAND Erase + Repartition + F.Reset*
Then under pit tab select the corresponding pit file for the rom you are currently flashing (DON'T select any other rom's pit file while flashing another rom)
Then begin flashing..
Flash all 3 stock roms using this until all 3 fail or someone works..
If odin succeeds to flash any rom without errors by miracle do this :
After odin reports flashed successfully.. you will still be in download mode.. hold volume down+home+power button to force reboot phone and the moment phone screen goes black (starts rebooting) change the keys you are holding to volume up+home+power button. The trick here is to go into recovery menu from download mode directly without booting into phone..
Once in recovery do a factory data reset + clear cache and then reboot..
Tell me how it goes.. and Good Luck !
Click to expand...
Click to collapse
Well here are the results. I took special precautions to do this all very methodically and not rush it. First I installed the most recent rom. No odin errors but when finished and I followed the instructions to go to recovery straight from download screen, it instead went right back to the boot loop saying "recovery booting". Next I installed the rom from January - exact same results. Next I installed the rom from the 935U - same exact results. Next I installed the combination rom. It installed without errors but when it rebooted, it automatically went to the recovery menu. I enter the option for reboot and the phone rebooted back to the recovery menu. This time I wiped cache and factory data reset, then rebooted. From there the phone rebooted to the screen that says factory binary and the arrows across the bottom of the screen. After a minute or so, it froze on that screen. A few minutes later the screen went black. Pressing PWR reboots to the same factory binary screen that freezes. Pressing VOLUP+HOME+PWR repeats the entire sequence from the recovery menu. Leaving the phone sit for a few minutes the SBL ERROR UPLOAD MODE screen appears.
I want to thank you for helping me in this process, it looks like I might be at the end of the road until the Verizon stores re-open after the pandemic calms down a bit.
Thanks again, take care!
shah22 said:
So it means your phone is in a recovery bootloop even after reflashing with odin .. very strange indeed.. looks like somehow your nv data (efs) got corrupted because any firmware issue would have been solved by a reflash.. or maybe even a hardware issue. I m sorry i ran out of ideas you will need to take it to service centre guys .. good luck.
Edit : here is the combination file for your phone :
https://androidfilehost.com/?fid=4349826312261742312
Extract and flash it using the AP tab of odin (it doesn't require 4 separate files in odin)
Then follow this thread :
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
Do what it said in OP BUT APPLYING THE COMBINATION ROM AND NORMAL ROM I PROVIDED ABOVE. Try both methods. Good luck
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
CAN you provide me combination software for G935FD U7 Binary??
G935FXXU7ETA9
i opened my phone a week ago to unplug batter the board says G935F/FD i have dm verification failed issue with frp lock on(thats my fault)
After updating to latest bootloader i flashed twrp and then root my phone bur i dont know why i made a mistake by turning off oem unlock and then restarted my phone
My phone is dead for weeks i need help
Just need U7 binary for Exynos version Also you can check my post about it Any way to fix it??
https://forum.xda-developers.com/s7-edge/help/rip-s7-edge-g935fd-one-help-t4082203
Mod notice:
Moved the thread, so any reference above to posting in the wrong forum is no longer valid.
Didgeridoohan said:
Mod notice:
Moved the thread, so any reference above to posting in the wrong forum is no longer valid.
Click to expand...
Click to collapse
Thanks a lot sir, won't want anyone bricking their device following my procedure ?
When people are already turning oem unlock off 'accidentally' these days ?
Sent from my S7 Edge using XDA Labs
Hi everyone,
I got an old SM-T510 from a friend, that doesn't want to boot. He already tried to factory reset it or fix it with the Smart Switch tool, but all of that didn't work. And who knows what else he tried... well at least I don't know.
So now I wanted to try to re-flash the stock firmware on it. I got the device into the recovery menu, selected "reboot to boot loader" which leads to a blue screen with a download icon.
If I now connect it to my computer and open up Odin, it is recognized.
The next challenge was to find the correct firmware. I used Samloader, typed in the model number, and needed a CSC. I assumed the device was bought here (Switzerland) so typed in AUT. Got a firmware, loaded AP, BL and CSC file into Odin (3.14.4) and pressed start. After a few minutes, I got a satisfying green PASS, the device started to reboot.
After the Samsung Galaxy flash screen, I got an android loading animation for a moment, and..... the device rebooted... and rebooted and stopped rebooting.
Finally it showed these error messages: "Can't load Android system. Your data may be corrupted.... you may need to perform a factory reset..." but if I do one, I still get the same result. At the bottom of the screen it says "Reboot recovery cause is [unknown]" "Reason is [enablefilecrypto_failed]" "Failed to load bitmap installing_text for locale en-US"
Do you have any advice on how I can fix this? Do I have a wrong CSC? Is something wrong in my procedure?
Any help is really appreciated.