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.
Where did you find such sboot.img.tar file?
death.by.confusion said:
Where did you find such sboot.img.tar file?
Click to expand...
Click to collapse
Here
https://forum.xda-developers.com/ga...ow-to-fix-sim-cards-didnt-read-j730f-t3939685
Michelyn50 said:
Here
https://forum.xda-developers.com/ga...ow-to-fix-sim-cards-didnt-read-j730f-t3939685
Click to expand...
Click to collapse
First, can you try installing any custom rom, blindly(since you said the screen is black when you boot in recovery).
Second, can you try flashing stock firmware without the BL part in Odin?
death.by.confusion said:
First, can you try installing any custom rom, blindly(since you said the screen is black when you boot in recovery).
Second, can you try flashing stock firmware without the BL part in Odin?
Click to expand...
Click to collapse
I tried blindly many times flashing any custom rom but with no luck since it's really hard predicting the buttons location on the screen, I probably need another phone replica with working twrp to mimick the exact moves.
For stock firmware, I manage to install it without BL but when booting it's just stuck on the Samsung logo, and when booting into stock recovery nothing just black screen, and booting into download mode it seems that the installation didn't change the binary -1, since I could see it on the screen
death.by.confusion said:
First, can you try installing any custom rom, blindly(since you said the screen is black when you boot in recovery).
Second, can you try flashing stock firmware without the BL part in Odin?
Click to expand...
Click to collapse
This is a screenshot when I try to install stock firmware (with BL)
https://m.imgur.com/a/9vuFqTX
Can you try flash other sboot files from the link you gave me? Try to flash some sboot file, and then make full flash of your stock firmware.
If not, maybe you can try flashing sboot with heimdal https://www.glassechidna.com.au/heimdall/
I have the same issue, any help or advice?
Flash último bootloader e modem CP
Flash Any Custom ROM
Did you flash misc partition ?
If your device keep booting in blackscreen, you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
The guide is for REDMI NOTE 9, so if you try to perform the method 1, you can cause more damages to your device.
Please, follow METHOD 2 only !
If TWRP is not working perfectly, obviously you need to flash stock rom recovery.img.
Good luck
Related
hello everyone, after rooting and flashing lots of phones, i have probably managed to brick one
since i am using linux, i tried heimdall wich detected but couldnt flash , not even read pit
i tried to root it, with kingroot, failed
then i tried kingoroot desktop app, it seemed to work then after flashing philzcwm using rashr, it went into download mode
at some time i may have flashed a recovery img onto BL, wich i NOW know is the bootloader
i knew that i shouldnt mess with the bootloader, but didnt think BL was bootloader
now using odin 3.10.6 in win xp it doesent seem to do nothing
it automatically goes into download mode with first line saying
"could not do normal boot"
i am now downloading an original firmware 4.4.6 from sam mobile
can anyone help me or is it bricked?
Lost count of how many things you did wrong there
Get a Native Windows 7+ PC running, boot the phone into download mode, flash stock ROM with ODIN 3.10.7
If it fixes it - spend a long time reading threads here on XDA before trying anything else
i dont think i flashed the bootloader, i remembered, odin was crashing before i ever hit start cause i was selecting the md5 and it didnt have the tar
now after flashing twrp 2.8 it boots fine, but if i try to boot in recovery, it goes to download mode "cant do normal boot"
flashed cf autoroot it also goes to download mode
i remember on galaxy s3 if you didnt restart straight to recovery just after flashing it would overwrite with stock recovery
but now if i try to restart to recovery after flashing it doesent do anything, i have to unplug it and take out the battery
edit
if i press vol[-] home power it goes to normal download mode
if i press vol[+] home power it supposed to go to recovery but goes to download mode with "could not do normal boot" message
if i press power alone it boots normally
in download mode it says
product name: sm-g901f
current binary:custom
system status:custom
reactivation lock: off
knox warranty void 0x1(4)
qualcomm secureboot: enable (csb)
RP SWREV: S1 T1 R1 A1 P1
secure download : enable
UDC start
i dont mind learning but android is pretty ugly with all the lack of documentation and standards
i learned a lot of stuff reading this forum, and will always respect people who know more than me
i just dont understand what the hell just happened, didnt encountered this before
Yea.. So follow my instructions
i am following your instructions precisely , will spend the day installing crap win7 wich i am running away from, to use with 3.10.7
in the meantime can you explain to me what happened?
i read somewhere something about odin bad usb on xp, would that pe hardware, driver, odin or usb protocol error
fixed, was flashing klte recovery, damn dozen versions of every phone
only clean rom i found was cm12 and dokdo7, both 5.1 based
waiting for network unlock, and case and im good to go
would have loved more after-market roms omni,aokp,pac, maybe 4.4
5.1 has the crap pie (position independent executable) so i cant play with perl 5.20, im stuck with 5.7
if anyone knows where to find more clean roms for g901f / kccat6xx i would be greatful
a more recent version of perl to work on 5.1 would also be nice
did you ever get this fixed?
having the same trouble with my Note4...just happened out of nowhere.
broad_st_bully said:
did you ever get this fixed?
having the same trouble with my Note4...just happened out of nowhere.
Click to expand...
Click to collapse
His last post says he fixed it...
*Detection* said:
His last post says he fixed it...
Click to expand...
Click to collapse
this phone is making me think I'm crazy...after pure hell all day yesterday and last night I wake up (after accepting the fact the phone was R.I.P.) and it turns right on and lets me set up after a factory reset.
This happened yesterday too though so I'm not gonna get all happy yet...
broad_st_bully said:
this phone is making me think I'm crazy...after pure hell all day yesterday and last night I wake up (after accepting the fact the phone was R.I.P.) and it turns right on and lets me set up after a factory reset.
This happened yesterday too though so I'm not gonna get all happy yet...
Click to expand...
Click to collapse
S5 or NOTE 4?
Could not do normal boot odin mode
I just rooted my phone so i can install a rom on my sm-n900s but i didnt realise that it was for an sm-n900.I flashed it on my phone with flashify and now all i can do is go to my custom recovery TWRP to wipe everything but still to no avail.I really do not know what to do.PLS HELP :crying::crying::crying::crying::crying:
zpimp said:
fixed, was flashing klte recovery, damn dozen versions of every phone
only clean rom i found was cm12 and dokdo7, both 5.1 based
waiting for network unlock, and case and im good to go
would have loved more after-market roms omni,aokp,pac, maybe 4.4
5.1 has the crap pie (position independent executable) so i cant play with perl 5.20, im stuck with 5.7
if anyone knows where to find more clean roms for g901f / kccat6xx i would be greatful
a more recent version of perl to work on 5.1 would also be nice
Click to expand...
Click to collapse
How did you fix it ??? if i flash a custom rom i get the same issue and my device is the same as yours. I flashed back stock rom, samsungs own recovery works well but as soon as i flash a custom recovery (twrp-3.0.0-0-klte-klte.img.tar or philz_touch_6.57.8-klte.tar.md5) i get your issue. How can i fix this and install a custom recovery ? When i install CF-Auto-Root-kccat6-kccat6xx-smg901f.tar.md5 the recovery is back but even when i flash within the os (terminal) the recovery is broken "again"
FIXED!!!! Installed CWM-based Recovery v6.0.5.1
MichelN said:
How did you fix it ??? if i flash a custom rom i get the same issue and my device is the same as yours. I flashed back stock rom, samsungs own recovery works well but as soon as i flash a custom recovery (twrp-3.0.0-0-klte-klte.img.tar or philz_touch_6.57.8-klte.tar.md5) i get your issue. How can i fix this and install a custom recovery ? When i install CF-Auto-Root-kccat6-kccat6xx-smg901f.tar.md5 the recovery is back but even when i flash within the os (terminal) the recovery is broken "again"
FIXED!!!! Installed CWM-based Recovery v6.0.5.1
Click to expand...
Click to collapse
Download stock rom and flash by odin.They are plenty of websites online.Just search for ur phone model followed by stock rom and u will find the exact rom for u to download and flash via odin.
The problem was the recovery, same as the user on page 1. See my last notes in prev. post
I've gotten no help at all with this. Very unlike this forum. My phone is a kltevew, which is straight talks version of a g900v. I need help, there are lots of great looking Roms that require you to have mm firmware I'd like to try!
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
ddjr said:
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
Click to expand...
Click to collapse
Download it with samfirm http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 (Model= SM-G900V Region= VZW) or from sammobile http://www.sammobile.com/firmwares/database/SM-G900V/ , do you know how to flash firmware with odin?
I do. Thanks so much for responding. Every time I try with Odin, a few different releases, it always gives me the error message fail. Can it be done with flashfire?
What stands in the log of odin when the flash completes?
Ill have to do it again to see... Be back in a bit!
I think it says FAIL! modem but I'll have to run it again... Brb
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
ddjr said:
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
Click to expand...
Click to collapse
Have you enabled the option to flash bootloader on flashfire setting?
What? No, I haven't... but do do right now. Thanks for the tip! Actually, where would I find it?
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
ddjr said:
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
Click to expand...
Click to collapse
It's in setting of flashfire...but only do it if odin doesn't work because do it from flashfire is more riskiy...
1)do a backup
2)check the bootloader flash option
3)install the firmware with all the wipe except internal storage(it mean that flashfire delete /data excluding /data/media/0 (sdcard) but include it in your backup copy because you never know )
4)wait till reboot skip setup wizard "spamming" the next button then install the rom with flashfire or twrp
On the flashfire site i found this:
Flash bootloaders
"This setting controls if FlashFire will attempt to flash bootloader partitions. By default, bootloader partitions are only read and never written. Even when enabled, flashing bootloader partitions may not succeed - many devices have protections in place against the bootloaders being overwritten.
Please note that flashing bootloaders is extremely dangerous. Any bug, error, or failure may result in an unrecoverable hard-brick. Do not use this feature unless you know exactly what you are doing.
Due to the danger of this feature, it is automatically turned off every time FlashFire starts. You have to manually re-enable it every time you want to use it.
If you must flash bootloaders, it is advised to use a bootloader-based flashing tool such as fastboot or ODIN to do it, as these are the safest methods. OTAs may also update bootloaders, and though slightly less safe than fastboot/ODIN, it is still much safer than having FlashFire flash bootloader partitions directly."
So i suggest to try to flash the firmware directly from odin first
No dice... still doesn't boot up past the red Verizon logo
ddjr said:
No dice... still doesn't boot up past the red Verizon logo
Click to expand...
Click to collapse
did you install the firmware in the "AP" box on odin? (after you factory reset your phone)
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
ddjr said:
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
Click to expand...
Click to collapse
Redownload the firmware extract it again,factory reset your phone,and try to install the firmware,maybe it's a bad download
Should I be flashing a kernel too? Will it even start/boot without the right kernel?
find out if you phone is refurbished. to install stock ROM you would need the main board and boot to be the same model.
if it's not, then you just need to install bootloader/modem without full ROM. look around in xda for bootloader/modem.
Was running Temasek's CM13 on a rooted, unlocked note 3. Somehow during a flash, I ended up with a restart to the Note 3 screen and hangs there. I always do a backup prior to my flashing, so there's one there but now there's no twrp for me to get to? Do I restart the process over (flash OS via Odin, reroot, reunlock, etc)? Or is there something different I need to do bc my phone is unlocked as a developer? Please help and thank you
?hang budged?
^^^ that's indecipherable; try again.
It is unlikely that you will need to start from scratch, but let's start with this:
Will the phone boot into *any* mode, including Odin Download mode?
Try pulling the battery, reinserting, and booting with
Vol-Up+Home+Power (recovery)
Vol-Down+Home+Power (Odin)
If you can get into Odin mode and it still says "Developer" you should be able to reflash twrp using Odin.
stoph8n24 said:
Somehow during a flash, I ended up with a restart to the Note 3 screen and hangs there.
Click to expand...
Click to collapse
OK, that's better than "hang budged"
stoph8n24 said:
...but now there's no twrp for me to get to?
Click to expand...
Click to collapse
You state that as a question... what happens when you try booting to the recovery or to Odin (download mode) using the button combinations as suggested?
Restoring a custom recovery to an unlocked bootloader phone using Odin:
Code:
cp twrp-3.0.2-0-hltevzw-4.4.img recovery.img
tar -H ustar -c -f OdinInstallTWRP.tar recovery.img
md5sum OdinInstallTWRP.tar >> OdinInstallTWRP.tar
mv OdinInstallTWRP.tar OdinInstallTWRP.tar.md5
Flash OdinInstallTWRP.tar.md5 using Odin (v3.0.9 or so) in the AP slot and be happy.
This ONLY works if the phone still has MODE: DEVELOPER showing on the Odin (Download) screen.
cheers
.
Lost developer mode, had to reinstall all the steps then insert my primary sdcard with the backup, then restore my last backup. Wasn't a hassle, just didn't know if I need to flash a something totally different since my phone is recognized as a developer now. Thank you, I did download twrp to flash in case it happens again.
stoph8n24 said:
Lost developer mode
Click to expand...
Click to collapse
The only way that would have happened is if you overwrote the bootloader with stock firmware ("aboot" in particular) or - even less likely - that your CID got changed somehow.
Unless you are saying that you intentionally flashed a full stock firmware set in Odin in order to effect the repair... then it would make sense.
What were you flashing that caused the original trouble?
bftb0 said:
The only way that would have happened is if you overwrote the bootloader with stock firmware ("aboot" in particular) or - even less likely - that your CID got changed somehow.
Unless you are saying that you intentionally flashed a full stock firmware set in Odin in order to effect the repair... then it would make sense.
What were you flashing that caused the original trouble?
Click to expand...
Click to collapse
I actually think I may have flashed the partial firmware instead of the modem firmware that I wanted. But looking at my laptop, I have firmware for so many different notes it's ridiculous. I wouldn't doubt that I just flashed the wrong file.
hi
ive got a s8, which was rooted using magisk, but was having issue, so was advised to unroot, remote and try superSU instead.
in the process of flashing stock rom AND 8.0, the phone now boots up to black screen showing verification failed, only option to reset.
when i press reset, all it does is restarts, loads up TWRP which had been installed before,
TWRP runs some program and fails and then phone goes back to black screen showing verification failed.
ive booted it into download mode, in the hope that i can just start again by simply lashing fresh stock rom, but it connects to odin fine, but when i click start, it gives a red error every time.
so i cant access the standard recovery menu as ive got TWRP so that loads instead and it looks as that is corrupted and i cant flash new fresh rom from download as odin brings up issue
ive check another phone and there is no issue with odin or the usb-c cable,
there is an issue with the s8 and odin does not like something in the s8 so wont let me flash anything to it,
any advice would be greatly appreicated.
When you flashed the stock rom using odin did you flash a bootloader aswell as the rom or did you just flash the rom the problem might be that the bootloader was for pie and the rom is oreo or vice versa whenever I flash back to stock I fill all but one of the boxes in odin
i suspect it was all oreo, as i downloaded as a complete file but ill check and get back to you
thanks for advice.
It's been a few years since I've done anything like this.
I can get into the recovery menus and wiped the device. It still won't boot normally or in safe mode.
Also if it's possible, what Rom would you recommend? I'm a Pixel user and really like it's UI.
kent c said:
It's been a few years since I've done anything like this.
I can get into the recovery menus and wiped the device. It still won't boot normally or in safe mode.
Also if it's possible, what Rom would you recommend? I'm a Pixel user and really like it's UI.
Click to expand...
Click to collapse
I recommend to first flash a stock firmware to fix the bootloop.
You can check and download stock Samsung firmware files with Frija (https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/) and then flash it with Odin.
Check latest stock firmware available for your device first then you can decide if you want to test a custom rom.
I flashed the official ROM but my phone hangs on Samsung logo screen. When I open stock recovery (as I don't have custom one), it says dm-verity verification failed and when I boot up my phone, it goes straight away to stock recovery and logs show recovery reason unknown no such file or directory. I have tried flashing multiple times but no luck. Odin flash is always successful.