Okay first post on this website.
4.4.2, i9505
So, as i am a compete android n00b, i rooted my s4 with the KingoRoot tool as i thought it was an easy method, later i found out ChainFire made an easy auto root .
After i rooted with the kingo my device would randomly reboot, when i called someone, when i locked my phone and random stages throughout the day.
After some reading online i found the solution was to re-flash my phone to stock fireware. so i downloaded odin, drivers, fireware from sam and tried to re-flash it. however my phone failed after aboot.mbn. I then got the unexpected error saying the phone had to be plugged into kies etc.
I then used "philz_touch_6.07.9-i9300.tar.md5" to get rid of the error message which worked. however the phone still would radnomly restart.
Again i turnrf to the web to find a solution for the radnom booting and found this -
http://forum.xda-developers.com/showthread.php?t=2514703
telling me to delete everythinhg knox basically. after deleting everything outlined my phone is now stuck on the samsung logo.
i cannot access recovery mode! however can access download mode. but i have tried multiple times to re-flash to stock firmware to no avail...
Help, please
Recap
- Stuck on samsung logo
- Cant access recovery mode
- Can access download mode
- Deleted everything knox as specified
Thanks, Dylan
1. The error that give u ODIN is coz you are trying to flash an older firmware that the one you have installed in your device.
2. You have to flash a STOCK recovery. Flash this file via ODIN in PDA/AP (like in the pic 1 attached): HERE.
3. Turn off your device manually when the process finish. Boot it into STOCK RECOVERY by pressing and holding Volume Up, Home and Power.
4. Take a look the CSC (pic 2). "Applied the CSC-code: ............" <- This is your REAL CSC. Turn off your device again manually and boot it into DOWNLOAD MODE by pressing and holding Volume Down, Home and Power.
5. Go to Sammobile and download the LATEST firmware for your device with correct CSC and flash it via ODIN.
6. About KNOX and reboots: Delete all KNOX reminds less "Lib = libknox_encryption.so".
7. Good luck
Hi,
I really am in a hurry. Using this phone for work as well as personal.
My phone is SM-N910C. Had 5.1.1 COI4 installed, rooted with cf-auto-root through Odin and after checking everything was ok setting SeLinux to permissive with the app found in this forum. Installed latest TWRP and flashed this with it (zip on first post) http://forum.xda-developers.com/lg-g2/general/guide-how-to-make-viper4android-lollipop-t3075794
Phone got stuck on Android is starting... Starting apps. After 20 minutes or so, wiped everything on the phone through Advanced wipe on TWPR. Phone doesn't restart, stuck on initial Note4 white letters (no Samsung splash screen) and recovery doesn't work.
Download (volume down etc) works. Tried to flash the COI4 again through ODIN but it fails all the time. Phone says sw rev. check fail device 2 binary 1... and now everytime I connect the USB phone gets stuck at a grey battery charging icon, even when I unplug it.
What can I do?
THANKS!
Got it! It was because phone installed an OTA update thus blocking bootloader to lesser versions. Updated to COJ5 and everything is fine.
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.
so i rooted my first android device about 6 hours ago went great. how ever i made a rookie mistake and turned off the oem unlock after I was finished now I'm stuck and fear i may have hard bricked my device, i used odin 3 with twrp 3.0.2 and installed the supersu even made backups using both twrp recovery and titanium backup. but when i rebooted my device im stuck in the boot loop with a red message stating custom binary blocked by frp lock. and recovery mode is not accessable, only option is download mode. ok so i tried to go back to the stock rom but i get custom binary(recover) blocked by frp lock. is there a solution here or did i prema brick my phone.
im not new to the modding process i have done a few other devices just never rooted a phone before today.
any ideas on what i should try next
FISBANREGNER said:
so i rooted my first android device about 6 hours ago went great. how ever i made a rookie mistake and turned off the oem unlock after I was finished now I'm stuck and fear i may have hard bricked my device, i used odin 3 with twrp 3.0.2 and installed the supersu even made backups using both twrp recovery and titanium backup. but when i rebooted my device im stuck in the boot loop with a red message stating custom binary blocked by frp lock. and recovery mode is not accessable, only option is download mode. ok so i tried to go back to the stock rom but i get custom binary(recover) blocked by frp lock. is there a solution here or did i prema brick my phone.
im not new to the modding process i have done a few other devices just never rooted a phone before today.
any ideas on what i should try next
Click to expand...
Click to collapse
any help with this would be great im looking for the latest firmware for the sm-g550t1 the rev00 doesnt work because of version mismatch
FISBANREGNER said:
so i rooted my first android device about 6 hours ago went great. how ever i made a rookie mistake and turned off the oem unlock after I was finished now I'm stuck and fear i may have hard bricked my device, i used odin 3 with twrp 3.0.2 and installed the supersu even made backups using both twrp recovery and titanium backup. but when i rebooted my device im stuck in the boot loop with a red message stating custom binary blocked by frp lock. and recovery mode is not accessable, only option is download mode. ok so i tried to go back to the stock rom but i get custom binary(recover) blocked by frp lock. is there a solution here or did i prema brick my phone.
im not new to the modding process i have done a few other devices just never rooted a phone before today.
any ideas on what i should try next
Click to expand...
Click to collapse
ok so i was having an issue where i bricked my metropcs sm-g550t1 (galaxy on5) when i downloaded the stock rom for my phone i would get a sw mismatch D2 B1 error. the reason for this error is the update that came out in the beginning of 2017 changed the firmware version from PF1 to PL1. so if you are also having this problem when trying to unbrick your phone use the firmware for phone SM-G550T2 then use your twrp backup to unbrick but remember to turn the oem unlock on or you will brick your phone again
I tried to root my phone today but after reboot, it got stuck in the boot screen which says "Samsung Galaxy 8+". I can only go to the download mode. I tried downloading the stock firmware and tried to flash it using Odin but the flash always fails to give a Fail! (DeviceInfo) error.
I don't know what to do. I am afraid the phone is not charging as well, it the battery dries out my phone will be dead. What should I do?
Did you try and root the new AQG5 base? Flashing TWRP or CF Auto root will fail if you do so. If this is the case then follow the guide @Nameless provided https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857 and throw him a thanks.
If you didn't do that and Odin still continues to fail when flashing stock you should give Smart Switch a try and go for an emergency recovery. You will need your device model number and S/N code ready. http://www.samsung.com/dk/smart-switch/
i have the equal problem my s8 stay in boot screen and in odin fail stock firmware! plz help me TT i can go the download mode but cant flash stock rom with odin