[sm j730f] Bootloader fail and TWRP boots into black screen - Samsung Galaxy J7 Questions & Answers

Greetings everyone,
I decided to post my problem with my phone after searching the entire internet for similar problem but with no luck. Anyway I used to play around with my Samsung j7 pro for 2 years, I managed to flash twrp and thus many other custom roms, until last week when I recklessly flashed a sboot.img.tar file through Odin in order to fix cellular network in a rom I flashed earlier, this alone bricked my phone refusing to get past the Samsung logo, so like I do always, I tried to restore my phone by flashing the stock firmware (9.0) which I always keep on my PC, but surprise, the phone refuses to go through the process and gives me this error:
sw rev check fail bootloader device -1 binary 6
(same with 8.0 and 7.0 firmware)
I searched the internet for same error but with no luck, because I understand it's a mismatch between device bootloader current version and the firmware bootloader's, that they should be the same or higher, meaning you can't downgrade, I get that! but I never seen device with negative figure (-1) what that's supposed to mean? my device bootloader used to be on 6, how did it managed to jump to minus one ?
then I tried to flash TWRP to see if I could flash a rom and get around it, so I did, but when booting into recovery the screen goes black, I thought first the phone turned off, but not really, because TWRP seems to work with screen completely black, I knew that because I accidentally touch the screen and I sense vibration, I managed to reboot the phone via twrp just by guessing the buttons location (screen always black) in order to prove that TWRP is working with screen off. I tried to flash multiple TWRP versions but the same problem, no screen just touch, by the way there is nothing wrong with display hardware because it shows Samsung logo at start and also can boot into download mode just fine.
I hope someone could help me overcome this big of an issue, because I tried everything.

Related

(sOLVED) my note is stuck on Samsung boot screen!!

i upgraded my note N8000 via odin mobile pro with success and everything was smooth and the root was not intact
I tried to flash a theme via mobile odin but was not success, but note was still ok
then 2 days later I tried to enter the recovery mode , i found the note stuck on samsung boot screen and dose not reboot, I can enter download mode but can not enter recovery mode to reflash even the stock rom
what to do?
should i reflash the CWM as 1st time? then reflash the root if i found it is gone?
or i have to reflash the stock rom first via odin desk top since i can not reboot the note? problem is the stock rom is on the note and do not have it on PC
the note now is on Samsung boot screen, how to turn it off since note can not remove the battery?
EDIT 1::good:
Flashed a stock recovery via odin desk top, and rebooted
Note is back alive , no wipes, every thing still there, root still here
Rebooted once again with success
rebooted into recovery (stock since I lost my CWM) with success
EDIT 2
Flashed CWM and my note is back for my modifications
:fingers-crossed:
Stock Recovery File?
thermax04 said:
i upgraded my note N8000 via odin mobile pro with success and everything was smooth and the root was not intact
I tried to flash a theme via mobile odin but was not success, but note was still ok
then 2 days later I tried to enter the recovery mode , i found the note stuck on samsung boot screen and dose not reboot, I can enter download mode but can not enter recovery mode to reflash even the stock rom
what to do?
should i reflash the CWM as 1st time? then reflash the root if i found it is gone?
or i have to reflash the stock rom first via odin desk top since i can not reboot the note? problem is the stock rom is on the note and do not have it on PC
the note now is on Samsung boot screen, how to turn it off since note can not remove the battery?
EDIT 1::good:
Flashed a stock recovery via odin desk top, and rebooted
Note is back alive , no wipes, every thing still there, root still here
Rebooted once again with success
rebooted into recovery (stock since I lost my CWM) with success
EDIT 2
Flashed CWM and my note is back for my modifications
:fingers-crossed:
Click to expand...
Click to collapse
Do you have a link to where you found the stock recovery rom/image? And how did you flash it? I am having a similar problem right now.
kyleschepis said:
Do you have a link to where you found the stock recovery rom/image? And how did you flash it? I am having a similar problem right now.
Click to expand...
Click to collapse
do u mean the stock rom? I got it from samobile.com
or u mean u want the stock recovery?
try this
http://mirror21.downloadandroidrom....e10.1/recovery/N8000_StockRecovery.tar?token=
Will reflashing the tablet to stock, delete all of my files off of it? Is there a way to retrieve the files through download mode somehow?
kyleschepis said:
Will reflashing the tablet to stock, delete all of my files off of it? Is there a way to retrieve the files through download mode somehow?
Click to expand...
Click to collapse
in my post i wrote that reflashing the stock rom did not wipe (delete) any thing, u will find all your stuff undeleted
thermax04 said:
in my post i wrote that reflashing the stock rom did not wipe (delete) any thing, u will find all your stuff undeleted
Click to expand...
Click to collapse
It says you flashed a stock recovery. Is it the same case for a stock ROM?
kyleschepis said:
It says you flashed a stock recovery. Is it the same case for a stock ROM?
Click to expand...
Click to collapse
sorry, my mistake, flashing the stock rom will not delete your stuff, just be sure to flash the same rom or higher, not lower one
So, I tried flashing the stock recovery and that did not work. And then I tried flashing the stock rom (multiple times with different roms) and that did not work either. My tablet is still stuck on the screen that says "Samsung Galaxy Note 10.1". Do you have any other suggestions?
can u write some details about what was before and reason for problem, to think together about a solution
thermax04 said:
can u write some details about what was before and reason for problem, to think together about a solution
Click to expand...
Click to collapse
My Note 10.1 N8013 was rooted, had TWRP, and Cyanogenmod 10.2 Nightly on it. I hadn't touched it in two days and went to turn it on. It wouldn't turn on, so I assumed it was dead. I charge it overnight and try to turn it on in the morning, but it just goes into a boot loop. The tablet says "Samsung Galaxy Note 10.1" and stays that way until it dies. If I boot into recovery mode, the Teamwin (TWRP) title screen pops up and then immediately disappears. The tablet then shows the battery loading icon if it is plugged in. The icon shows up, then disappears and the shows up again and repeats this a few times. I could only boot into download mode successfully.
I have tried flashing different stock roms and recoveries through odin, including the one that you have linked on here. None of them have worked. I have also tried repartitioning the tablet, which passed on Odin, but did not solve the problem.
Other forums say that I should do a factory reset or wipe the data, but I do not know how to do this without being able to boot into recovery or the OS itself.
Thanks
P.S. I also brought it to Best Buy to see if the Samsung guy could reflash the stock rom, but his rom did not work either. They are all passing on Odin, so it isn't an error in that case.
I read that a lot of people got problems with Cyano roms. I did not like it and never used it, sorry can not help you
thermax04 said:
I read that a lot of people got problems with Cyano roms. I did not like it and never used it, sorry can not help you
Click to expand...
Click to collapse
Could it be because of the Cyanogen rom? I didn't update recently... I probably updated it a week before it died. Would you happen to know how to do a factory reset / wipe the data from the tablet, if I can't get into recovery mode or the OS?
I don't think that there is any other way, sorry about that.
try to put your problem in the Cyano rom thread, may others had the same and solved it
Ok thank you
Let me know if you get it fixed
Hi kyleschepis,
Let me know if you find a solution. I have a very similar issue . . . the difference is, I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started about 5 days ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But 5 days ago, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I am able to get into the Odin download mode but cannot get into recovery mode no matter what I do/
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00_user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. But the power + volume up combination does not get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for 5 days now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
robb-x said:
Hi kyleschepis,
Let me know if you find a solution. I have a very similar issue . . . the difference is, I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started about 5 days ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But 5 days ago, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I am able to get into the Odin download mode but cannot get into recovery mode no matter what I do/
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00_user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. But the power + volume up combination does not get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for 5 days now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
Click to expand...
Click to collapse
Did you try removing the sd card and reboot again ?
DId you fix your tablet
kyleschepis said:
Ok thank you
Click to expand...
Click to collapse
Hi Kysleschepis,
Were you able to fix the problem with your phone.
I have exact same problem....my Gt-n8000 tablet is stuck on "Samsung Galaxy Note 10.1" logo. And i cant access the recovery mode.
Let me know if you found a solution to this problem.
Thanks.
same here but didn't work
i have same problem with my Note 10.1 N8000 stuck in bootloop problem but i didn't do anything like upgrading or install new app ... its stuck by him self and i tried the following and all not working :
1, Hard Reset with software menu (not working)"only if the device is working".
2, Hard Reset with Dial secret code key(not working) "only if the device is working".
3, Hard Reset with Hardware Key Button(Factory recovery screen not working).
4, installing recovery philz_touch_6.07.9-n8000.tar with Odin (passed installed successfully but still not working).
5, installing recovery openrecovery-twrp-2.4.1.0-p4notewifi_3 with Odin (passed installed successfully but still not working).
6, installing recovery CF-Auto-Root-p4noterf-p4noterfxx-gtn8000.tar with Odin (passed installed successfully but still not working).
7, installing recovery twrp-2.6.3.1-n8000.tar with Odin (passed installed successfully but still not working).
8, installing recovery Samsung_N8000_Hard_Reset_File_JB in "CSC" field with Odin (passed installed successfully but still not working).
9, installing "N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar" full new Android OS with Odin (passed installed successfully but still not working).
Finlay there is No Samsung Service Center in my country, i need to send it by mail to nearest country have Samsung Service Center and will cost me a lot .. what i have to do
Weeshi said:
i have same problem with my Note 10.1 N8000 stuck in bootloop problem but i didn't do anything like upgrading or install new app ... its stuck by him self and i tried the following and all not working :
1, Hard Reset with software menu (not working)"only if the device is working".
2, Hard Reset with Dial secret code key(not working) "only if the device is working".
3, Hard Reset with Hardware Key Button(Factory recovery screen not working).
4, installing recovery philz_touch_6.07.9-n8000.tar with Odin (passed installed successfully but still not working).
5, installing recovery openrecovery-twrp-2.4.1.0-p4notewifi_3 with Odin (passed installed successfully but still not working).
6, installing recovery CF-Auto-Root-p4noterf-p4noterfxx-gtn8000.tar with Odin (passed installed successfully but still not working).
7, installing recovery twrp-2.6.3.1-n8000.tar with Odin (passed installed successfully but still not working).
8, installing recovery Samsung_N8000_Hard_Reset_File_JB in "CSC" field with Odin (passed installed successfully but still not working).
9, installing "N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar" full new Android OS with Odin (passed installed successfully but still not working).
Finlay there is No Samsung Service Center in my country, i need to send it by mail to nearest country have Samsung Service Center and will cost me a lot .. what i have to do
Click to expand...
Click to collapse
I have the same problem. I was just playing a game when it suddenly turned off and went to the boot screen. Also tried installing N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar.md5 (success but also didn't work). Still stuck at the "Samsung Galaxy Note 10.1" screen.
Also can't access recovery, or do a wipe before installing firmware (I think USB debugging isn't turned on).
Did you find any solutions yet?
Thanks.
el_roi said:
I have the same problem. I was just playing a game when it suddenly turned off and went to the boot screen. Also tried installing N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar.md5 (success but also didn't work). Still stuck at the "Samsung Galaxy Note 10.1" screen.
Also can't access recovery, or do a wipe before installing firmware (I think USB debugging isn't turned on).
Did you find any solutions yet?
Thanks.
Click to expand...
Click to collapse
Sorry till now no solutions ... If you have warranty on the device go to the samsung maintenance center i think its wrong factory made

Samsung Galaxy S6 (sprint variant) failed firmware flash FAC LOCK

Let me start by addressing I know this isn't the sprint thread but there's a lot more development here which equals more help. Plus this issue seems to be able to happen to any variant.
Second, this isn't my device I'm trying to see if it can be fixed for a friend. I'm not that familiar with Samsung devices but I have been able to get them working in the past via Odin or kies but this time I need some help.
So this is what's going on, my friend recently rooted his S6(SM-920P) not sure which method he used (don't think it matters at this stage) and was on stock rom (LP5.0.2) with xposed framework installed. He hadn't changed the kernel AFAIK oh but I did install TWRP for him and everything was working. Long story short he woke up a couple days ago to his phone being unable to turn back on. I told him how to get to download mode and I asked him what did it say on the top left corner it said something like "system binary not SEandroid locked" underneath that it said fac lock
So I had him give me the phone thinking somehow it did a OTA update while he was asleep or something either way I was confident using Odin to flash the firmware would solve the issue. Had the firmware finished flashing I'm confident it would have but halfway through Odin simply froze on installing system. I figured its just gonna take a while 45 mins later it was still stuck at the same spot.
Not really thinking about it I figured I will just reboot the phone back into download mode restart the process it should be fine. Not a good idea. Now all I get is a green screen saying to access the smart switch emergency recovery system. But it gets better.
My computer isn't recognizing the device now. I installed smart switch software and it's not recognizing it. I even installed Kies and it's not recognizing either.
Is his phone toast or what? I tried emergency system recovery but I need the S/N of his phone to possibly get this thing working again, but it boot into anything anymore except the screen that says Samsung switch...
PLEASE HELP ME if it's bricked it's bricked I get that but if there's a way to figure out what to do I'm all ears. Thanks in advance

Bricked/soft bricked SM-P905

Hello!
Around a month ago I installed a custom rom on my Samsung Galaxy Note Pro 12.2 (SM-P905), which ran smoothly until a week ago, when my tablet suddenly wouldn't leave the Samsung Galaxy Logo screen when booting. I was also unable to access recovery (I had TWRP installed), however I was able to access download mode. Then I decided to try to install the stock firmware using Odin. It seemed fine until it was about halfway through the installation, when it seemed to disconnect and the installation failed. After several attempts this still happened. I also tried installing both TWRP and CWM, both of which passed in Odin, however I am still unable to access recovery mode. I also tried installing the custom rom, with the same results as I mentioned earlier. In addition to this the screen has also begun flickering a whole lot, both when showing the Samsung logo and when in download mode, however it seems to intensify during the latter. This, in addition to the fact that I am unable to get any response when it isn't hooked up to my computer, has led me to believe that there is some issue with the battery as well, however I am absolutelly clueless at the moment.
I also have to mention that this is my first post here and my first attempt at installing a custom rom or doing anything of this nature to my devices. Any help would really be appreciated!
mbrau said:
. In addition to this the screen has also begun flickering a whole lot, both when showing the Samsung logo and when in download mode, however it seems to intensify during the latter. This, in addition to the fact that I am unable to get any response when it isn't hooked up to my computer, has led me to believe that there is some issue with the battery as well, however I am absolutelly clueless at the moment.
Click to expand...
Click to collapse
Your battery connector needs to be re soldered first before trying to flash firmware.
Read the threat " Flickering Screen " for more information. Cracked battery connector will cause flickering screen, reboot, hang on samsung logo at boot..etc...

Need help after failed rom install

I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.

Having various problems trying to flash my S7 out of a boot loop

Had it for 3 years now, it first looped in October 2017, broke all the sensors but has otherwise been working fine since. I also rooted it about 7 months ago in case that makes any difference with recovery. During both of these loops I have been unable to reliably get into recovery/download mode. I left it alone for an hour earlier today and came back to find that it was somehow in Odin/download mode with the text in the top left but still on the boot screen. So I plugged it into my computer, it was detected and then I flashed it with the correct G930T firmware and home csc. Got the success message in Odin and it seemed to be working but it was just stuck on the boot screen now. So now I've just been trying to flash it again with the other csc but it has been failing for a lot of different reasons and I don't know what any of them mean. I did manage to get it to power on a lot more reliably and into download mode, but still having problems. The biggest problem is when I get to either the download screen or warning screen, the screen suddenly gets all glitchy and I can't do anything. Whenever that happens it also shuts off after 10 seconds. This also happened on the Smart Switch emergency recovery screen when I cancelled a stalled flash and then tried to flash it again from that screen. I've also gotten errors when trying to flash from the download/boot screen. The ones I can remember are "unsupport dev_type", "secure check fail : tz eMMC write fail : tz" and "secure check fail : hyp eMMC write fail : hyp". I can't even find anything else on these errors and have no idea what they mean. I also have no idea how it is getting into Odin mode on the boot screen but so far that is the only way I have been able to do anything since I can't get into download mode the proper way. Lastly I tried to check in Smart Switch to recover it but it says the device is unsupported and there is nothing in emergency recovery.
Operation Ivy said:
Had it for 3 years now, it first looped in October 2017, broke all the sensors but has otherwise been working fine since. I also rooted it about 7 months ago in case that makes any difference with recovery. During both of these loops I have been unable to reliably get into recovery/download mode. I left it alone for an hour earlier today and came back to find that it was somehow in Odin/download mode with the text in the top left but still on the boot screen. So I plugged it into my computer, it was detected and then I flashed it with the correct G930T firmware and home csc. Got the success message in Odin and it seemed to be working but it was just stuck on the boot screen now. So now I've just been trying to flash it again with the other csc but it has been failing for a lot of different reasons and I don't know what any of them mean. I did manage to get it to power on a lot more reliably and into download mode, but still having problems. The biggest problem is when I get to either the download screen or warning screen, the screen suddenly gets all glitchy and I can't do anything. Whenever that happens it also shuts off after 10 seconds. This also happened on the Smart Switch emergency recovery screen when I cancelled a stalled flash and then tried to flash it again from that screen. I've also gotten errors when trying to flash from the download/boot screen. The ones I can remember are "unsupport dev_type", "secure check fail : tz eMMC write fail : tz" and "secure check fail : hyp eMMC write fail : hyp". I can't even find anything else on these errors and have no idea what they mean. I also have no idea how it is getting into Odin mode on the boot screen but so far that is the only way I have been able to do anything since I can't get into download mode the proper way. Lastly I tried to check in Smart Switch to recover it but it says the device is unsupported and there is nothing in emergency recovery.
Click to expand...
Click to collapse
When you flash with Odin tick "'re partition" in Odin options.
When "pass" appears disconnect phone from pc. Force reboot by holding home+volume down+power.
As soon as screen goes black press volume up while keeping home and power pressed. When recovery menu appears choose wipe / factory reset. Then reboot.
What is obviously very important is you are flashing the correct firmware for the device in the first place.

Categories

Resources