Hello all a few days ago I accepted the MI1 update from Verizon then flashed Hyper. I wanted to try CM 10.2 so I downloaded goo manager from the market and installed TWRP recovery went to boot and got stuck in download mode. I was able to get out of that and reflash safestrap recovery but I have no idea how to successfully flash CM10.2. I'm on Me7 what do I use to update and be able to install TWRP and successfully flash a non stock rom on my phone?
Sent from my SCH-I545 using Tapatalk
Kelsey Jones said:
Hello all a few days ago I accepted the MI1 update from Verizon then flashed Hyper. I wanted to try CM 10.2 so I downloaded goo manager from the market and installed TWRP recovery went to boot and got stuck in download mode. I was able to get out of that and reflash safestrap recovery but I have no idea how to successfully flash CM10.2. I'm on Me7 what do I use to update and be able to install TWRP and successfully flash a non stock rom on my phone?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
You can't install CM on anything but a MDK phone. Once you upgrade to anything past that you can no longer bypass the bootloader and are stuck using ROMs which are supported by Safestrap. AOSP and CM ROMs are not compatible.
The list of ROMs which work with Safestrap is available here: http://forum.xda-developers.com/showthread.php?t=2448726&highlight=safestrap
The bad news is that by flashing the MI1 update then flashing a nonstandard recovery, you've now probably tripped the Knox Warranty Void flag. That's not recoverable regardless of what you flash. (Try starting up in download mode - if the warranty void flag reads "0x1", you're toast.)
k1mu said:
You can't install CM on anything but a MDK phone. Once you upgrade to anything past that you can no longer bypass the bootloader and are stuck using ROMs which are supported by Safestrap. AOSP and CM ROMs are not compatible.
The list of ROMs which work with Safestrap is available here: http://forum.xda-developers.com/showthread.php?t=2448726&highlight=safestrap
The bad news is that by flashing the MI1 update then flashing a nonstandard recovery, you've now probably tripped the Knox Warranty Void flag. That's not recoverable regardless of what you flash. (Try starting up in download mode - if the warranty void flag reads "0x1", you're toast.)
Click to expand...
Click to collapse
Its says 0×0
Sent from my SCH-I545 using Tapatalk
That's good news. Get yourself back running safestrap and pick one of the compatible ROMs.
Can someone please explain how to use safestrap for me? I have the 4.3 Google Edition ROM on my SD card and safestrap installed, but I can't create a ROM slot. It says "Free Space: 12 MB" and the "Create ROM Slot" button is dim. What do?
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
I have purchased a galaxy nexus on the cheap to hold me over until the nexus 6 is out but if I can fix my note, I would like to.
I know there were other threads about this same issue but it seems that they are all on a different version of the note, or on a s3 or something. Not to mention, I don't see anything that I could try without asking for some help on here. Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Thanks guys!!!
amberkalvin said:
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
Click to expand...
Click to collapse
Before you tried to flash a custom ROM and things went wonky...were you on Verizon's factory stock 4.3 MJ9 firmware, or on Beanstown106’s modified 4.3 MJ9 with TWRP installed?
Does the phone still boot into stock recovery? If so, you may be able to fix the phone by doing a factory reset.
amberkalvin said:
Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Click to expand...
Click to collapse
If you were on Verizon's factory stock 4.3 MJ9, then you won't be able to Odin flash back to 4.1.2 or any earlier Android version because the bootloader has been locked down tight on 4.3 (and 4.4.2) with no current do it yourself method to unlock for those newer versions. You would want to restore the phone back to factory stock 4.3 though, if that's what version you were on before your phone got messed up. You can root the phone on 4.3 with saferoot, then use safestrap recovery to flash some custom Touchwiz ROM's.
If you were on the 4.1.2 based bootloader, (but running Beanstown106’s MJ9 firmware and TWRP), then you would want to restore your phone back to factory stock 4.1.2 and then root and unlock the bootloader again with CASUAL. This would give you the most flexibility with flashing custom kernels, ROM's, etc...
Check out Section 1b in Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. The guide has download links for the files you'll need to restore the phone back to the correct build version.
I'm run a Sprint Note 3 stock rooted 4.4.2 NC5 with Philz CWM version hltespr 6.12.9. I decided to update to 4.4.4 NK4. First, thought I would skip a step by not unrooting device and just did a factory reset. Then booted into download mode and Odin flashed NK4 ( I used a fresh copy from Sammobile 1.50gb zip ). When the flash was finished ( Passed on odin ) the device tried to start and bootlooped or what some might call a soft brick. Pulled the battery and then booted into recovery, and found to my suprise that the custom recovery was still installed. The Odin flash did not completely take, so while in recovery I wiped caches, data, and system.
Now from recovery booted into download mode and Odin flashed NK4 again. This time it installed properly and so I went back and forth from NC5 to NK4 about 6 times. Why, to check various things like signal strength ( about the same with both NC5 and NK4 basebands ) GPS ( found no problem with getting GPS to lock with NK4 ) Ram footprint ( at first boot up NK4 only slightly larger than NC5 ) . Of course going back to NC5 from NK4 resulted in bootloop or soft brick at boot up, the easiest way to fix this is to pull the battery boot into recovery do a factory reset, then Odin flash NC5 again. If you are the least bit timid about bootloops and soft bricks I don't recommend doing this.
Ok, so now I have a stock, recovery status ( official ) NK4 installed. Next installed a custom recovery, went with Philz CWM hltespr v6.12.9 ( this recovery is bulletproof ). I Odin flashed Philz and booted the device everything good. Next booted into recovery and flashed Super Su v2.40. Then booted back into NK4 everything running great used root checker and the device is rooted.
Now I have stock rooted NK4, so now to debloat the device started with KNOX. Went to SuperSu and clicked ok to disable KNOX, SuperSu froze at "disabling KNOX". I rebooted the device and downloaded Root Explorer then did a KNOX search and about 25+ files containing KNOX ( more than in NC5 apparently they added a few new ones to NK4 ) did a multi-delete and then rebooted device and it bootlooped at start up.
So back to square one, flashed Nk4, Philz recovery, and tried the experimental ( BETA ) SuperSu 2.4.3 version. Device booted up fine, tried to disable KNOX and again it froze at "disabling KNOX", again I tried to remove all the KNOX files with Root Explorer and it bootlooped again at start up. At this point I'm going to wait till Chainfire has a cf-autoroot for NK4 and a SuperSu that will disable KNOX. Went back to NC5 with everything running smooth as glass, hope this info is helpful. Enjoy !!!
jimzweb1 said:
I'm run a Sprint Note 3 stock rooted 4.4.2 NC5 with Philz CWM version hltespr 6.12.9. I decided to update to 4.4.4 NK4. First, thought I would skip a step by not unrooting device and just did a factory reset. Then booted into download mode and Odin flashed NK4 ( I used a fresh copy from Sammobile 1.50gb zip ). When the flash was finished ( Passed on odin ) the device tried to start and bootlooped or what some might call a soft brick. Pulled the battery and then booted into recovery, and found to my suprise that the custom recovery was still installed. The Odin flash did not completely take, so while in recovery I wiped caches, data, and system.
Now from recovery booted into download mode and Odin flashed NK4 again. This time it installed properly and so I went back and forth from NC5 to NK4 about 6 times. Why, to check various things like signal strength ( about the same with both NC5 and NK4 basebands ) GPS ( found no problem with getting GPS to lock with NK4 ) Ram footprint ( at first boot up NK4 only slightly larger than NC5 ) . Of course going back to NC5 from NK4 resulted in bootloop or soft brick at boot up, the easiest way to fix this is to pull the battery boot into recovery do a factory reset, then Odin flash NC5 again. If you are the least bit timid about bootloops and soft bricks I don't recommend doing this.
Ok, so now I have a stock, recovery status ( official ) NK4 installed. Next installed a custom recovery, went with Philz CWM hltespr v6.12.9 ( this recovery is bulletproof ). I Odin flashed Philz and booted the device everything good. Next booted into recovery and flashed Super Su v2.40. Then booted back into NK4 everything running great used root checker and the device is rooted.
Now I have stock rooted NK4, so now to debloat the device started with KNOX. Went to SuperSu and clicked ok to disable KNOX, SuperSu froze at "disabling KNOX". I rebooted the device and downloaded Root Explorer then did a KNOX search and about 25+ files containing KNOX ( more than in NC5 apparently they added a few new ones to NK4 ) did a multi-delete and then rebooted device and it bootlooped at start up.
So back to square one, flashed Nk4, Philz recovery, and tried the experimental ( BETA ) SuperSu 2.4.3 version. Device booted up fine, tried to disable KNOX and again it froze at "disabling KNOX", again I tried to remove all the KNOX files with Root Explorer and it bootlooped again at start up. At this point I'm going to wait till Chainfire has a cf-autoroot for NK4 and a SuperSu that will disable KNOX. Went back to NC5 with everything running smooth as glass, hope this info is helpful. Enjoy !!!
Click to expand...
Click to collapse
just freeze the knox **** with titanium easier.
jimzweb1 said:
I'm run a Sprint Note 3 stock rooted 4.4.2 NC5 with Philz CWM version hltespr 6.12.9. I decided to update to 4.4.4 NK4. First, thought I would skip a step by not unrooting device and just did a factory reset. Then booted into download mode and Odin flashed NK4 ( I used a fresh copy from Sammobile 1.50gb zip ). When the flash was finished ( Passed on odin ) the device tried to start and bootlooped or what some might call a soft brick. Pulled the battery and then booted into recovery, and found to my suprise that the custom recovery was still installed. The Odin flash did not completely take, so while in recovery I wiped caches, data, and system.
Now from recovery booted into download mode and Odin flashed NK4 again. This time it installed properly and so I went back and forth from NC5 to NK4 about 6 times. Why, to check various things like signal strength ( about the same with both NC5 and NK4 basebands ) GPS ( found no problem with getting GPS to lock with NK4 ) Ram footprint ( at first boot up NK4 only slightly larger than NC5 ) . Of course going back to NC5 from NK4 resulted in bootloop or soft brick at boot up, the easiest way to fix this is to pull the battery boot into recovery do a factory reset, then Odin flash NC5 again. If you are the least bit timid about bootloops and soft bricks I don't recommend doing this.
Ok, so now I have a stock, recovery status ( official ) NK4 installed. Next installed a custom recovery, went with Philz CWM hltespr v6.12.9 ( this recovery is bulletproof ). I Odin flashed Philz and booted the device everything good. Next booted into recovery and flashed Super Su v2.40. Then booted back into NK4 everything running great used root checker and the device is rooted.
Now I have stock rooted NK4, so now to debloat the device started with KNOX. Went to SuperSu and clicked ok to disable KNOX, SuperSu froze at "disabling KNOX". I rebooted the device and downloaded Root Explorer then did a KNOX search and about 25+ files containing KNOX ( more than in NC5 apparently they added a few new ones to NK4 ) did a multi-delete and then rebooted device and it bootlooped at start up.
So back to square one, flashed Nk4, Philz recovery, and tried the experimental ( BETA ) SuperSu 2.4.3 version. Device booted up fine, tried to disable KNOX and again it froze at "disabling KNOX", again I tried to remove all the KNOX files with Root Explorer and it bootlooped again at start up. At this point I'm going to wait till Chainfire has a cf-autoroot for NK4 and a SuperSu that will disable KNOX. Went back to NC5 with everything running smooth as glass, hope this info is helpful. Enjoy !!!
Click to expand...
Click to collapse
What version of Odin are you using and where did you get your tar files from? I'd like to try flashing back to NC5 from NK4 to gain root without tripping Knox until something other than cf-auto can root NK4.
Sent from my SM-N900P using Tapatalk 2
biggdevon said:
What version of Odin are you using and where did you get your tar files from? I'd like to try flashing back to NC5 from NK4 to gain root without tripping Knox until something other than cf-auto can root NK4.
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
Read through this thread should answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440
on my thread I list micmars as he has a great XDA site for .tar files. However I got the tar. files from here http://www.sammobile.com/firmwares/. If flashing back to NC5 results in a bootloop DON"T PANIC !!!! Just pull the battery boot into recovery and wipe cache and do a factory reset. Than pull the battery and boot into download mode and flash NC5 again. One thing on the second flash be PATIENT, after odin finishes and says PASSED " DO NOT UNPLUG THE DEVICE " you will notice at this point is where a blue flash line starts that is the recovery the last thing being flashed !!! It takes about 3 to 5 minutes after you see PASSED your device screen will dim and it will start up for first time use.
Your process worked like a charm for me. Fully rooted stock NC5 from NK4 using towelroot. Is there anyway to retain root and go back to NK4?
Sent from my SM-N900P using Tapatalk 2
biggdevon said:
Your process worked like a charm for me. Fully rooted stock NC5 from NK4 using towelroot. Is there anyway to retain root and go back to NK4?
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
No, sorry NH7 closed the exploit used by Towelroot in NC5. It has not been updated for NH7 or NK4. If you use Towelroot, cf-atuoroot, or De La Vaga root on NH7 or NK4 you will trip KNOX !!!
If your KNOX warranty is tripped like mine then root with SuperSU. Just flash in a custom recovery for any version of KitKat you want to root. If you have not already checked look at my thread http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 I changed the rooting instructions. Enjoy !!!
So is it possible to flash nc5 nh7 or nk4 tars at any time . I'm on nk4 full firmware and baseband .. just wanna make sure .. THNX FOR THIS INFO
chico260 said:
So is it possible to flash nc5 nh7 or nk4 tars at any time . I'm on nk4 full firmware and baseband .. just wanna make sure .. THNX FOR THIS INFO
Click to expand...
Click to collapse
Yes, I have done it many times now. As I stated above just be aware that a bootloop can occur going back to NC5 from NH7 or NK4. Don't Panic just follow the instructions above and it's smooth sailing. Besides the info above you can check out my flashing thread here http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
jimzweb1 said:
Yes, I have done it many times now. As I stated above just be aware that a bootloop can occur going back to NC5 from NH7 or NK4. Don't Panic just follow the instructions above and it's smooth sailing. Besides the info above you can check out my flashing thread here http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
Click to expand...
Click to collapse
Also will the one click work going from nk4 to nc5?
Im on NH7 modem and baseband and im trying to go to Nk4 modem but I get this error on Odin 3.07
EDIT: I got it
Jocutz1987 said:
Im on NH7 modem and baseband and im trying to go to Nk4 modem but I get this error on Odin 3.07
EDIT: I got it
Click to expand...
Click to collapse
You need remove SIM card when fresh the ROM, maybe helpful. Should see all pass here instead of any fail.
Hey there guys,
I have been up since 10pm trying to get this thing going and I have the phone running just no wi fi and no success at all with any recovery. I dug up and found out that I needed Safestrap because of my MDF version. However, this safestrap STILL does not enable recovery! I have used TWRP, CWM and PHILZ and I cant even get into recovery to do a ROM install!
If you guys can help me, I would appreciate it.
I have attached the picture for you guys to help me out!
Safestrap will not allow you install a custom recovery, Safestrap is your only option.
Custom recoveries such as TWRP, CWM, or Philz can only be installed on an MDK device. This is because an exploit called "Loki" is required to do so. This exploit only works on the MDK bootloader versions due to a loophole that was present. This loophole has been closed in all versions released after MDK.
Hi!
I have a verizon s4 i545 on android 5.0.1 OC1.I rooted it and then tried to install cwm recovery in order to install custom roms.But after the recovery proccess didn't go well and after reboot i am stuck on Software update failed message.I tried to install stock rom 5.0.1 oc1 via odin but at the end of flashing it was always fails.I tried to find verizon software assistant but nowhere.One version i found wasn't installing on my computer.What can i do in order to bring my phone back to life?Thanks!