Related
Haven't rooted a phone in a little but am generally pretty savvy. I can get into recovery, tried restoring factory settings and clearing cache, same result unfortunately. I tried running an Odin .exe I found in another thread but it just opens and closes.. :/
When in download mode, product name: SMN900V, System Status: Custom
Knox Kernel Lock: 0x0, Knox Warranty Void: 0x0, Qualcomm Secureboot: Enable (CSB), RP SWREV: S1, T1, A3, P1
Write Protection: Enable, UDC START
Any help anyone can offer or provide a working rom or flashable file to get me booted would be most appreciated! No idea what ROM or Android version he put on this thing (purchased from Swappa).
TIA!!
Re download Odin and tar file. Have you gotten Odin to flash anything or does it fail or do you mean Odin itself isn't working? It sounds like you didn't extract Odin files and just opened it.
Sent from my SM-N900V using XDA-Developers mobile app
I was able to flash a Verizon firmware (thru Odin) and get it booted but I don't have root (seller claimed he did beforehand). Sounds like I should start with unlocking bootloader or root first? Thanks for the response man, I appreciate all the help I can get!
Sent from my SM-N900V using XDA-Developers mobile app
Start with the root first. Can't unlock the bootloader without it.
Awesome is there a one click by chance or is it complicated?
Sent from my SM-N900V using XDA-Developers mobile app
DNak206 said:
Awesome is there a one click by chance or is it complicated?
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.
I just got note3 Verizon, I rooted it couple days ago. I am on tmobile, so far everything works with stock lollipop except hotspot. Contemplating on unlocking boot loader at the moment.
santas16 said:
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.
Click to expand...
Click to collapse
[threadjack]
I was fooling around with flashing custom recoveries from within a rooted ROM today, and found something useful - when I "got stuck at bootloader" because TWRP failed to boot. So long as the main ROM is still bootable and is rooted, you can clear the "always tries to boot the recovery" behavior the following way:
1) Pull the battery (and plug back in after a couple seconds)
2) Vol-Down+Home+Power (as if you are trying to enter Download mode)
3) When you get the Custom ROM Warning menu, choose Cancel (not Continue)
This clears the BCB (Boot Communication Block) in eMMC and the phone will thereafter attempt to boot normally, rather than continuing to try to boot the recovery again. The sequence #2-3 does not work if you don't start by pulling the battery - if you soft-boot by holding the Power button down (~ 15 seconds), the phone will always attempt to boot the (broken) recovery, whether you enter Odin mode or Cancel.
Well, that's the way my phone behaves at this moment. (I am using a older bootloader however - it is always possible that this is a bootloader behavior that changed in later versions). Anyway - if you get "stuck" again, this could save you some labor, rather than having to go back to Odin, flash everything, and re-root.
Having said that, I'm not sure what you would use as alternative custom recovery. You could do something like pull just the stock kernel from the OF1 and re-pack it into your own customization of TWRP to see if that changes anything. Thing is, I could have sworn I saw a report from someone who said they are using TWRP 3.0.2 with the OF1 bootloader successfully.
Are you using "twrp-3.0.2-0-hlte.img" ?
[/threadjack]
bftb0 said:
[threadjack]
I was fooling around with flashing custom recoveries from within a rooted ROM today, and found something useful - when I "got stuck at bootloader" because TWRP failed to boot. So long as the main ROM is still bootable and is rooted, you can clear the "always tries to boot the recovery" behavior the following way:
1) Pull the battery (and plug back in after a couple seconds)
2) Vol-Down+Home+Power (as if you are trying to enter Download mode)
3) When you get the Custom ROM Warning menu, choose Cancel (not Continue)
This clears the BCB (Boot Communication Block) in eMMC and the phone will thereafter attempt to boot normally, rather than continuing to try to boot the recovery again. The sequence #2-3 does not work if you don't start by pulling the battery - if you soft-boot by holding the Power button down (~ 15 seconds), the phone will always attempt to boot the (broken) recovery, whether you enter Odin mode or Cancel.
Well, that's the way my phone behaves at this moment. (I am using a older bootloader however - it is always possible that this is a bootloader behavior that changed in later versions). Anyway - if you get "stuck" again, this could save you some labor, rather than having to go back to Odin, flash everything, and re-root.
Having said that, I'm not sure what you would use as alternative custom recovery. You could do something like pull just the stock kernel from the OF1 and re-pack it into your own customization of TWRP to see if that changes anything. Thing is, I could have sworn I saw a report from someone who said they are using TWRP 3.0.2 with the OF1 bootloader successfully.
Are you using "twrp-3.0.2-0-hlte.img" ?
[/threadjack]
Click to expand...
Click to collapse
I get a different kind of stuck, I'm not going to try it again but it said the phone has detected software that is not authorized or something along those lines. I cannot just pull battery as it just repeats over and over. I actually do not ever get to enter any recoveries at all, it automatically detects that's it's not the original bootloader and tells me such. anyways, I had to reload the image and take the OF1 update again... all is working back to normal.
I had used "twrp-3.0.2-0-hltevzw-4.4.img" from the twrp manager app, flashed via app, restarted to end up having the error message immediately on bootup of device... no recoveries or anything could load. I would have to assume the 4.4 means kk version and that's why it didn't work?
santas16 said:
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.
Click to expand...
Click to collapse
Hmmm. Maybe I was reading something into your post that wasn't there. I assumed that you had also performed the retail-to-dev edition CID change "unlock" after you gained root on OF1. Is that wrong - did you simply flash a recovery after getting root?
In my case I flashed a non-bootable TWRP (dd of=/dev/block/mmcblk0p15...) onto the recovery; doing this tripped my Knox Warranty flag, but otherwise the bootloader didn't complain about unauthorized software. After figuring out how to clear the "always try to boot the recovery" near-disaster, I used a 2.8.x TWRP series custom recovery successfully (In addition to flashing the stock recovery back into place and verifying that it still worked) But this is on a truly ancient bootloader (MJ7), so maybe all bets are off about expecting later bootloaders to behave in this same fashion.
Still, the point of developer edition functionality is to allow for custom boot (& recovery) partitions, so it's surprising that you were getting warnings like that if your phone was in developer mode.
@santas16
Hey. For what it's worth, I was able to boot twrp-3.0.2-hltevzw-4.3.img from my SM-N900V ... with a MJ7 bootloader!
But not the hltevzw-4.4.img. (That could be due to the old bootloader however, I don't know for sure)
Note that my phone has the retail-to-deved CID change that puts it into developer mode. (I used @donc113 's executable with adb)
This allows unsigned boot or recovery partitions to proceed to load/execute, but it will burn your Knox Warranty flag (which is unimportant to me at this point). I think that is actually the expected behavior when the phone is in developer mode.
I've been flashing all sorts of recoveries without worrying whether they will boot or not (as I know I can get back into the rooted ROM to flash into place a working version)**
Probably the best advice about not getting stuck in the "continually tries to re-enter the recovery" mode is to NOT use "reboot to recovery" methods (in Safestrap, other recoveries, or root-privileged Apps (flashfire?)), but to always shut the phone down to a powered-off state, and just use the three-button startup method (Vol-Up+Home+Power) to enter the recovery. That way nothing is being written into the BCB that will make it want to loop back to a failed recovery.
cheers
** what was interesting is that I could successfully boot any of the MI9, MJ7, MJE stock recoveries on my MJ7 phone. Moreover, the bootloader would not pop up the yellow "Set Warranty Bit: recovery" message right before they loaded. The NC4 recovery would not boot to a menu, but it also did not present a "Set Warranty Bit: recovery" message. I presume this means that the boot layer is not looking for exact version matches, but rather just checking that the Samsung signing operation is correct. I could not boot OB6 or OF1 recoveries; somewhat curiously though, these attempts *would* throw the "Set Warranty Bit: recovery" error message even though they are validly signed Samsung recoveries. I don't know if it is a reasonable hypothesis, but I think that indicates that Samsung may have altered the details of their signing verification method someplace between NC4 and OB6 so that earlier bootloaders fail this check. Ugh. As if there weren't enough details already.
If your bootloader is still 0F1 then download flashify from Google and hit recovery and tap top twrp.. Your all set...sounds like a lot of craziness for nothing.
Sent from my SM-N900V using XDA-Developers mobile app
santas16 said:
I get a different kind of stuck, I'm not going to try it again but it said the phone has detected software that is not authorized or something along those lines. I cannot just pull battery as it just repeats over and over. I actually do not ever get to enter any recoveries at all, it automatically detects that's it's not the original bootloader and tells me such. anyways, I had to reload the image and take the OF1 update again... all is working back to normal.
I had used "twrp-3.0.2-0-hltevzw-4.4.img" from the twrp manager app, flashed via app, restarted to end up having the error message immediately on bootup of device... no recoveries or anything could load. I would have to assume the 4.4 means kk version and that's why it didn't work?
Click to expand...
Click to collapse
If you get the " not authorized or something along those lines" error, it means you're not unlocked.
Today i was trying to install the Android Marshmallow 6.0.1 on my Galaxy S5 Snapdragon via Odin, i downloaded the firmware from Sammobile, i verified that the phone model was exactly the same as named on the firmware, i place the .md5 file in the AP slot and everything was ready to go! (The phone was already plugged and in Bootloader mode, and drivers were up to date) then when finishing the flash Odin FAILS to complete the flash and the phone is left with nothing than the Download mode, i panic and try to access recovery mode but realize that there´s no recovery....I proceed to install the recovery.tar into my phone and it works, i start the phone and Samsung logo comes up, finally it loads and does al the process after you flash a Samsung phone.
Everything works just fine!...except for one thing, THERE´S NO RECOVERY!!!. The phone works perfectly but when i try to enter recovery mode, it sends me to Odin mode as it displays a message saying that failed to boot into recovery.
Please help me i don´t know what to do.
Thanks!
Just flash a custom recovery like twrp or cwm
Already did...same problem, recovery won't boot
adavicco said:
Already did...same problem, recovery won't boot
Click to expand...
Click to collapse
You need to flash a pit file to complete the install correctly.
I was trying to root my phone
odin failed and my phone showed "Custom Binary (Recovery): Blocked By FRP Lock"
I was following this video
https://www.youtube.com/watch?v=M8ji0yjf7IY
What went wrong ?
johngr77 said:
Probably you forgot to enable OEM unlock in developer options menu
Click to expand...
Click to collapse
I did that and I successfully installed the twrp file
Then the phone rebooted and now it is stuck in the Samsung logo !!
What should I do ?
look through this forum - i only put the answer on here yesterday
JUST FLASH with latest stock firmware.. 1st of all to get phone into main screen/ activation lock screeen
asadnow2k said:
JUST FLASH with latest stock firmware.. 1st of all to get phone into main screen/ activation lock screeen
Click to expand...
Click to collapse
I did that and its working again
But How can I root it now ?
I tried rooting it again the same way but it got stuck on logo screen again !
is there any alternative way to root it ?
HussainJH said:
I did that and its working again
But How can I root it now ?
I tried rooting it again the same way but it got stuck on logo screen again !
is there any alternative way to root it ?
Click to expand...
Click to collapse
you just install frimware latest one and activate it with ur google account. than oem unlock than flash with root via odin
Im having this issue with my phone i accidently ticked off the oem unlock in development settings I put the phone in download mode because thats the only mode i can get into (recovery and regular boot does not work) when I connect to pc now it shows up as usb serial device in ports or it shows up as samsung modem and odin wont flash the firmware
I never had any issue. You get a single recovery.IMG and flash it. The s6e+ is tricky. You should have a custom ROM or what you want to flash ready and just flash twrp, boot immediately into it. Backup phone via twrp then wipe it and flash custom ROM. This will ensure you don't get any real issues or fpr blocked. Also use XDA tuts or get help here, YouTube can go good or bad. Recovery images are device specific. If you have f and flash t it won't work. You have to really look at what you are flashing and match model information. I'm seeing a lot of people fpr blocked and in trouble. I might go make a little walkthrough
I successfully rooted my phone but it got stuck in a bootloop when I restarted it.
I can't enter recovery mode or turn it off, all I can do is enter odin mode.
I have tried:
1. The AGQ5 fix (https://forum.xda-developers.com/ga...g-aqg5-fix-t3636857/post73032395#post73032395) it doesn't work.
2. Smart switch, it says my device is unsupported
Please help!
1- flash twrp again
2- flash stock rom with odin ( download mode )
you can reboot just with vol - + shut down B
you maybe installed the wrong version of twrp the latest one is for the new bootloader if you have the older bootloader install the last version
It doesn't boot into TWRP even after I flash it again
djisgod said:
you maybe installed the wrong version of twrp the latest one is for the new bootloader if you have the older bootloader install the last version
Click to expand...
Click to collapse
Sorry if I'm asking a question but how do I check my bootloader version? I just used the latest version (twrp-3.1.1-0-herolte.img.tar) from a site but I can't link it.
popmpopm said:
1- flash twrp again
2- flash stock rom with odin ( download mode )
you can reboot just with vol - + shut down B
Click to expand...
Click to collapse
It doesn't boot into TWRP even after I flash it again
Flash full stock in odin. Then you can try twrp again if you wish.
It worked, thanks so much for all your help. Words cannot describe how grateful I am.
help
osidaksjdmw said:
It worked, thanks so much for all your help. Words cannot describe how grateful I am.
Click to expand...
Click to collapse
help me
how can did you get to download
HELP ! S8 Wont BOOT !!
I have the same problme! I can flash Combination file and then its booting and I can go to recovery mode ,but after when I flash again STOCK rom succesfully ,S8 wont boot Any Idea what is going on ? Im on U2CRED ....PLEASE HELP !!!!
zassamel said:
I have the same problme! I can flash Combination file and then its booting and I can go to recovery mode ,but after when I flash again STOCK rom succesfully ,S8 wont boot Any Idea what is going on ? Im on U2CRED ....PLEASE HELP !!!!
Click to expand...
Click to collapse
I can flash Combination file
Click to expand...
Click to collapse
What this supposed to me ?
samsung s8
StonebridgeGr said:
What this supposed to me ?
Click to expand...
Click to collapse
Combination File ,its AP witch allow you to bypass for example FRP lock
osidaksjdmw said:
I successfully rooted my phone but it got stuck in a bootloop when I restarted it.
I can't enter recovery mode or turn it off, all I can do is enter odin mode.
I have tried:
1. The AGQ5 fix (https://forum.xda-developers.com/ga...g-aqg5-fix-t3636857/post73032395#post73032395) it doesn't work.
2. Smart switch, it says my device is unsupported
Please help!
Click to expand...
Click to collapse
EXACT same problem. Put I cant flas anything via Odin. Not even TWRP. What do I do???
PLEASE help
benna said:
EXACT same problem. Put I cant flas anything via Odin. Not even TWRP. What do I do???
PLEASE help
Click to expand...
Click to collapse
why you cant? what error did it give you? might you dont have drivers installed on your pc?
StonebridgeGr said:
why you cant? what error did it give you? might you dont have drivers installed on your pc?
Click to expand...
Click to collapse
ODIN MODE
DOWNLOAD SPEED : FAST
NAME: SM-G950F
CURRENT BINARY: CUSTOM
SYSTEM STSTUS : CUSTOM
RMM STATE: PRENORMAL
FAP LOCK: OFF
OEM LOCK : OFF
SECURE DOWNLOAD: ENABLED
SW REV. CHECKFAIL(BOOTLOADER) DEVICE :2 BINARY :1
I can ONLY boot into download mode.
When switching on the phone , I get the Galaxy S8 logo by Samsung with the red writing on the top:
"Only officiall released binaries are allowed to be flashed"
Flashing original firmware via ODIN just fails.
"Complete (write) operation failed !!" is the error in Odin.
I tried different versions of Odin , original firmware and boot loaders suggested on XDA. All just fails.
So my phone is just dead.
I had the lasted firmware on ( OTA update about a week ago)
I installed TWRP now , roooted with Magisk , all was fine untill I rebooted the phone.
So drivers and all are fine , everything worked until I rebooted the phone.
Please help. What to do now. I need my phone !!!
PLEASE
Hi, i have a Samsung S10 plus 128gb that was interupted when it was going to get new image and twrp. Belive i was doing it wrong order :S
Now i cant get out off download mode.
Get this error message:
ODIN MODE (AVB Fail)
recovery: Error validating footer. (0)
recovery: Error verifiying vbmeta image: invalid vbmeta header (6)
CUSTOM RECOVERY
VBMETA G975FXXU4BTA8, 28787933R
Is there any way to solve this? Would be happy if there is...
robibo said:
Hi, i have a Samsung S10 plus 128gb that was interupted when it was going to get new image and twrp. Belive i was doing it wrong order :S
Now i cant get out off download mode.
Get this error message:
ODIN MODE (AVB Fail)
recovery: Error validating footer. (0)
recovery: Error verifiying vbmeta image: invalid vbmeta header (6)
CUSTOM RECOVERY
VBMETA G975FXXU4BTA8, 28787933R
Is there any way to solve this? Would be happy if there is...
Click to expand...
Click to collapse
Probably you'll need to flash stock rom via Odin.
Or via Smart Switch.
And this is a wrong forum for S10 plus.
w41ru5 said:
Probably you'll need to flash stock rom via Odin.
Or via Smart Switch.
And this is a wrong forum for S10 plus.
Click to expand...
Click to collapse
Thanks for answering, i will try this later today and get back. I saw that i put it in wrong section will try to remove it.
Is there any other way then Odin for flashing Rom? I have tried and get error.
Im using Samfirm to download the Rom and Odin for flashing. I have used Odin without problems before but now its not working :S
Im stuck at the moment someone with some suggestions?
Solved
robibo said:
Solved
Click to expand...
Click to collapse
How?
Midyr said:
How?
Click to expand...
Click to collapse
Sorry for the late answer, i used odinr downloading the stock firmwire into the phone but i used samfirm instead to download newest version and when i setup the odin i did almost as when i root it but didnt uncheck the reboot function i let it be checked and the phone downloaded the stock firmwire and started to work as it should.
Whats up with your phone? Where does it stuck?
robibo said:
Sorry for the late answer, i used odinr downloading the stock firmwire into the phone but i used samfirm instead to download newest version and when i setup the odin i did almost as when i root it but didnt uncheck the reboot function i let it be checked and the phone downloaded the stock firmwire and started to work as it should.
Whats up with your phone? Where does it stuck?
Click to expand...
Click to collapse
hey, got stuck at the same downloadmode boot screen (from normaly booting after installing twrp via Odin) but with this at the end: G975FXXU4CTC9 29996307R.
the rest is exactly the same. bevor i had the Problem that twrp coundt write System. flashed stock Samsung and now i cant Flash a working twrp. tried official&custom twrp. Nothing seems to work. Need help.