Related
Hey guys,
I decided that I wanted to root my phone for a custom rom. I used towelroot and odin to root my phone. It rooted successfully.
Heres where the problem is:
I installed twrp, and scrolled through menu options so I could install a Recovery. However, whenever I tried to install the rom, it would always take me to the default boot menu, therefore i was unable to get a rom. Long story short, twrp has caused my download mode menu to enable write protection. I went onto supersu, and removed my root. I just want to go back to factory/ stock rom and remove root. I downloaded samsungs firmware from their site and tried using odin, but this gives me a fail and states that "complete (write) operation failed".
My phone displays:
SGH-I337
Samsung Official
Custom system status
Knox kernal lock: 0x0
Knox Warranty viod: 0x0
CSB-config-lsb 0x30
write protection: enable
eMMC burst mode enable
I have tried to flash it back to stock so many times. Now I am getting a msg that says "firmware upgrade encountered an issue" -kies does not help remove this.
-I am using the original cable
-I can only boot into recovery and download mode.
-My main goal is to go back to stock.
Akluu said:
Hey guys,
I decided that I wanted to root my phone for a custom rom. I used towelroot and odin to root my phone. It rooted successfully.
Heres where the problem is:
I installed twrp, and scrolled through menu options so I could install a Recovery. However, whenever I tried to install the rom, it would always take me to the default boot menu, therefore i was unable to get a rom. Long story short, twrp has caused my download mode menu to enable write protection. I went onto supersu, and removed my root. I just want to go back to factory/ stock rom and remove root. I downloaded samsungs firmware from their site and tried using odin, but this gives me a fail and states that "complete (write) operation failed".
My phone displays:
SGH-I337
Samsung Official
Custom system status
Knox kernal lock: 0x0
Knox Warranty viod: 0x0
CSB-config-lsb 0x30
write protection: enable
eMMC burst mode enable
I have tried to flash it back to stock so many times. Now I am getting a msg that says "firmware upgrade encountered an issue" -kies does not help remove this.
-I am using the original cable
-I can only boot into recovery and download mode.
-My main goal is to go back to stock.
Click to expand...
Click to collapse
What firmware version are you on? You're probably going to have to use odin to get your phone working correctly again.
Sent from my Nexus 5 using XDA Free mobile app
Akluu said:
Hey guys,
I decided that I wanted to root my phone for a custom rom. I used towelroot and odin to root my phone. It rooted successfully.
Heres where the problem is:
I installed twrp, and scrolled through menu options so I could install a Recovery. However, whenever I tried to install the rom, it would always take me to the default boot menu, therefore i was unable to get a rom. Long story short, twrp has caused my download mode menu to enable write protection. I went onto supersu, and removed my root. I just want to go back to factory/ stock rom and remove root. I downloaded samsungs firmware from their site and tried using odin, but this gives me a fail and states that "complete (write) operation failed".
My phone displays:
SGH-I337
Samsung Official
Custom system status
Knox kernal lock: 0x0
Knox Warranty viod: 0x0
CSB-config-lsb 0x30
write protection: enable
eMMC burst mode enable
I have tried to flash it back to stock so many times. Now I am getting a msg that says "firmware upgrade encountered an issue" -kies does not help remove this.
-I am using the original cable
-I can only boot into recovery and download mode.
-My main goal is to go back to stock.
Click to expand...
Click to collapse
What firmware are you on?
If you upgraded past 4.4.2 mdlish then you have to safestrap.
Sounds like a soft brick to me, you have to Odin back and try again.
Make sure you Odin back to what you have/had or your stuck forever with safestrap.
If you don't know how to Odin read the giant back to stock guide.
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.
Hello, this is my first post.
Introduction
So today & yesterday I tried rooting my stock ROM, Android M 6.0.1 G900F Galaxy S5 but I've had a few problems with it.
Details
I think I've done everything correctly to try to flash TWRP onto my phone:
Downloading the lastest version of TWRP-klte (I've used 3.0.2-1 & 3.0.2-2)
Unticking 'Auto-Reboot' in Odin (I've used Odin3_v3.09 & Odin3_v3.10.6)
Pull out the battery to get out of download mode, etc.
But nothing seems to work. When I go into download mode it tells me:
Code:
[B][COLOR="Red"]ODIN MODE[/COLOR]
[COLOR="Black"]PRODUCT NAME: SM-G900F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x0[/COLOR]
[COLOR="DimGray"]QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1[/COLOR]
[COLOR="Blue"]SECURE DOWNLOAD: ENABLE[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
[/B]
To my understanding I find it weird that it says my Current Binary and my System Status say 'Custom' but my KNOX is still 0x0.
Now, of course before I tried to flash TWRP it said I my Current Binary and my System Status said 'Official'.
What I Think Is The Problem
Correct me if I'm wrong but I think the problem is that UDC START part in the download mode.
I've read online that some people get that when their phone is in a bootloop but I have no problem with my phone.
Conclusion
In conclusion I think that the problem may be resolved by factory restoring my phone, but if you have any other ideas, please reply to this thread.
Thanks.
None of those steps would root your phone though
TWRP is a custom recovery, once you've flashed that, you need to boot into TWRP, and flash SuperSU 2.xx beta (xx = whichever is the latest version)
Then you can reboot into Android and should be rooted
*Detection* said:
None of those steps would root your phone though
TWRP is a custom recovery, once you've flashed that, you need to boot into TWRP, and flash SuperSU 2.xx beta (xx = whichever is the latest version)
Then you can reboot into Android and should be rooted
Click to expand...
Click to collapse
The problem is that it won't let me flash TWRP. I have SuperSU on my device ready to be flashed but I need to get TWRP working.
Ah I see, and you are booting straight into recovery after replacing the battery?
1. Disable auto reboot & Flash TWRP
2. Disconnect USB & Pull battery to power off once flash is complete
3. Replace battery and boot immediately into TWRP
TWRP 3.0.2.0 Klte is the version I use
*Detection* said:
Ah I see, and you are booting straight into recovery after replacing the battery?
1. Disable auto reboot & Flash TWRP
2. Disconnect USB & Pull battery to power off once flash is complete
3. Replace battery and boot immediately into TWRP
TWRP 3.0.2.0 Klte is the version I use
Click to expand...
Click to collapse
Yes I booted once into recovery straight after flashing and it never worked.
Now I have to use ADB because it's a bit finicky and it wont always boot into recovery by doing Volume Up + Power.
I'll try using 3.0.2.0 and see what happens.
Edit: I just tried with Odin 3.09 & TWRP klte 3.0.2.0, still no luck. Also couldn't boot into recovery with buttons, had to use Volume Up + Power.
-removed
I don't know if I can root again my j5. Yesterday I installed a custom recovery (twrp) in j5 2015 (v 6.0.1 marshmallow) and root my device successfully. Then by mistake I untick oem unlock and restart my phone. Then I got a message saying " Custom binary locked by frp or fap don't remember exactly. I installed Samsung kies 3, enter download mode and flash new firmware successfully. Today I was about to install custom recovery again and when I went into download mode, I noticed something different. Warranty void 0x1 (2) I google it but in every forum, every post it showing that have in front know but in my phone its just saying "warranty void 0x1 (2)" anyway my question is if I can install again custom recovery and root without bricking my device because of this message. Please answer soon.
hronis said:
I don't know if I can root again my j5. Yesterday I installed a custom recovery (twrp) in j5 2015 (v 6.0.1 marshmallow) and root my device successfully. Then by mistake I untick oem unlock and restart my phone. Then I got a message saying " Custom binary locked by frp or fap don't remember exactly. I installed Samsung kies 3, enter download mode and flash new firmware successfully. Today I was about to install custom recovery again and when I went into download mode, I noticed something different. Warranty void 0x1 (2) I google it but in every forum, every post it showing that have in front know but in my phone its just saying "warranty void 0x1 (2)" anyway my question is if I can install again custom recovery and root without bricking my device because of this message. Please answer soon.
Click to expand...
Click to collapse
Yes just go ahead and never disable OEM unlock.
Okay, so I have hard bricked my Note 3. I know, I know...months back my phone died out and I got a new phone on MetroPCS. So I didn't really try to do anything with it. It would load to the Verizon screen and go no further. Well I dropped my new MPCS phone in some (a lot of) water and after dismantling and cleaning it, its dead and buried. So, for now I was going to see if I could reflash stock software for my Note 3 and enable the LTE bands for Tmobile. Blah blah, long story short. I flashed TWRP and it worked, I went to reboot it after a wipe and I think I deleted everything. I used the OF1 unbrick img to see what would happen because there was no PL1 linked, and I get:
Boot Recovery Mode
Check boot partitions
Copy from T-Flash
Boot Recovery
Write 163840 Sectors
Flash Write Failure
ddi : mmc_read failed
Odin Mode
Product Name: SM-N900V
Current Binary: Samsung Official
System Status: Custom
Reactivation Lock: Off
Qualcomm Secureboot: Enable (CSB)
AP SWREV: S1, T1, A1, A4, P1
Secure Download: Enable
UDC Start
So, a sign of life...however I can't get into download mode. I think I need a PL1 unbrick image to get it there. Any takers on making me one? I've read the Unbrick hard brick forum and the farthest anyone has gone was to OF1 so I didn't know if anyone was running a PL1 version that could make the image for me. Please let me know.
Thanks In Advance
huskiesmike said:
Okay, so I have hard bricked my Note 3.
Thanks In Advance
Click to expand...
Click to collapse
Is your boot loader unlocked? If not you must use Odin to flash full stock ROM and recovery. The N900V will not boot with a custom recovery unless the boot loader is unlocked. You need a working, rooted phone with a CID # that starts with 15 in order to unlock the boot loader.
Bootloader is unlocked and it was rooted, obviously not now but I had no issue running TWRP before.
huskiesmike said:
Bootloader is unlocked and it was rooted, obviously not now but I had no issue running TWRP before.
Click to expand...
Click to collapse
Did the unbrick image replace the boot loader? I have not used/need the unbrick image and I'm not sure what is in it. If boot loader is unlocked and TWRP is working you should be able to flash any n900v ROM to get it working. I'll look at the unbrick image, if I can find it.
Well, it had TWRP. I installed TWRP with the intention of flashing a new ROM to it because it was soft-bricked and stuck on the VZW flash screen. When I rebooted it didn't respond. The only response I have now is the Recovery boot mode with the OF1 unbrick.img and it won't go into download mode or recovery. No response at all without the SD card in it.
Thanks