Related
I just rooted a Verizon GS4 (VRUAME7) using this method. Everything went fine. I verified root with Root Checker, rebooted the phone, checked again.
Then I followed this method to install TWRP. When I rebooted the device as instructed, it got stuck on a splashscreen that has and Android logo and says "Downloading...Do not turn off target!!" :'(
The upper left in red says "Could not do normal boot. ODIN MODE"
I tried a battery pull, vol dwn + power, vol up + power and vol down + up + power.
How do I get back to normal boot or into TWRP recovery? I have a ROM I'd like to install, and as of now...it won't get past that splash screen.
What do I do?
Thanks!
First off youre in the wrong section. Questions go in the Q and A section. Second your on the me7 ota and you cant install a custom recovery/roms on the me7 ota. To get your phone booting again you will have to flash the stock recovery (not sure if someone has posted a stock recovery flashable via odin as I havent looked)or flash me7 again.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
First off youre in the wrong section. Questions go in the Q and A section. Second your on the me7 ota and you cant install a custom recovery/roms on the me7 ota. Not yet at least. I havent ran into this problem myself so I dont know an exact fix. To get your phone booting again you will have to flash the stock recovery (not sure if someone has posted a stock recovery flashable via odin as I havent looked)or flash me7 again (which will work without a doubt).
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Where was there a note about ROMS not working on ME7. I didn't see that anywhere.
Regardless, how do I fix it?
dreamliner330 said:
Where was there a note about ROMS not working on ME7. I didn't see that anywhere.
Regardless, how do I fix it?
Click to expand...
Click to collapse
In the thread about the me7 update.
Also in the 500 or so threads where people freaked out when they couldn't ROM anymore after they took the update.
Or in the bounty thread.
Sent from my SCH-I545 using xda premium
^I didn't update.
dreamliner330 said:
^I didn't update.
Click to expand...
Click to collapse
if your on me7 then you updated..
Sent from my SCH-I545 using xda app-developers app
Check this thread
http://forum.xda-developers.com/showthread.php?t=2301259
Sent from my SCH-I545 using xda app-developers app
elliwigy said:
if your on me7 then you updated..
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I didn't. Perhaps it automatically did it or it was updated when I got it, as I don't recall manually doing it.
Regardless. What do I do now?
I already posted how to fix it ............ if you dont know how to restore your phone via odin then you have a small amount of reading to do and then your phone will be back up and running in no time :thumbup:
Sent from my SCH-I545 using Tapatalk 2
dreamliner330 said:
I didn't. Perhaps it automatically did it or it was updated when I got it, as I don't recall manually doing it.
Regardless. What do I do now?
Click to expand...
Click to collapse
There are reports of it doing it over night.
To fix the phone find the full me7 Odin package and Odin it back to stock. Id link you but I have had no reason to have links for me7 packages yet.
Sent from my SCH-I545 using xda premium
dreamliner330 said:
Regardless. What do I do now?
Click to expand...
Click to collapse
I had this same problem trying to install TWRP. What I did to fix it was to boot into download mode (volume down + home +power) and then I got prompted for did I really want to do that, I responded no and the phone booted up.
Sent from my SCH-I545 using Tapatalk 2
thornev said:
I had this same problem trying to install TWRP. What I did to fix it was to boot into download mode (volume down + home +power) and then I got prompted for did I really want to do that, I responded no and the phone booted up.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Thank you. :victory:
This worked perfectly.
Hopefully it'll won't fall back into that. Can't wait until I can ROM this sucker. Laaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaag.
Since you have the update, boot the phone up in Odin mode and plug in your USB cable.
If you installed the desktop software you will have a Verizon folder in your start menu.
In that folder there should be an app "Verizon Software Upgrade Utility"
Run that and it should tell you you are up to date.
There is a repair utility within that app, run that and it should fix your problem.
It takes a while because it downloads the rom and then flashes it.
No guarantees, but I believe that will get you back to stock unrooted.
Sent from a Galaxy S4... Far far away
Sounds like he just got into download mode and didn't recognize it, and his rom, recovery, and everything was untouched.
To the OP, you're probably good if your phone has booted normally, works fine, and you're still rooted. You can't flash any roms or mods, but you can still apply some mods by simply pushing them to your /system partition, setting permissions, and rebooting. Either follow the instructions for which directory to put the file/files in, or you can open up a flashable zip and use the same path as the directories in the zip.
You should even be able to push a modded framework-res.apk and SystemUI.apk and rename the old ones, once people start building ME7 roms, though I can't guarantee it'll work. All you can do is try, and now you know how to get into Download mode to use Odin if it doesn't work.
As far as plain lag goes, just freeze alot of the bloat, there's around 50 apks (in MDK, anyway) that aren't doing anyone any good. Then grab a cpu app like Trickster Mod and see what, if any, parameters the stock kernel enables you to change. If you can set the Interactive cpu governor, Deadline scheduler, Performance gpu governor, and increase the read-ahead size, you should see a significant improvement.
:thumbup:
Sent from my SCH-I545 using Tapatalk 2
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Development is only for developers to post work
Thread moved
I tried rooting my S4 using motochopper and it didnt work or so it seemed. Phone booted up then updated to kit kat automatically. I noticed some phishy types of things on my phone so i decided to restore to factory and everything went to hell. I tried to reflash back to factory firmware using Odin 3.09 and I keep getting a fail. It seems ive tried a ton of different firmware downloads from various site with no luck. they are all supposedly factory. Kies doesnt work because i cant get a Serial number only a IMEI. I can get to the download screen to try flashing with odin but it always fails otherwise im stuck on the 'Firmware upgrade has encountered an issue. please select recovery mode in Kies and try again"
The top left corner says
ODIN MODE
PRODUCT NAME; SCH-I545
CURRENT BINARY; Samsung Official
KNOX KERNEL LOCK; 0x0
KNOX WARRANTY VOID; 0x0
CSB-CONFIG-LSB; 0x30
WRITE PROTECTION; Enable
eMMC BURST MODE enabled
Please help ive been doing this for hours with no luck. I tried sammobile firmwares. not all but I did try I545VRUEMK2 which i imagined was appropriate
You need to Odin the NC5 firmware if you took the OTA, you can't Odin full versions of older software like MK2.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
joshm.1219 said:
You need to Odin the NC5 firmware if you took the OTA, you can't Odin full versions of older software like MK2.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok i see what youre saying.t Well that would be strange if that works because stock i didnt have kit kat and verizon never let me update to it until i started messing around. I'm waiting for the NC5 file to download now.
chachachazippo2 said:
Ok i see what youre saying.t Well that would be strange if that works because stock i didnt have kit kat and verizon never let me update to it until i started messing around. I'm waiting for the NC5 file to download now.
Click to expand...
Click to collapse
Didnt work. I grabbed this file "I545VRUFNC5" from sammobile and still failed right away
joshm.1219 said:
You need to Odin the NC5 firmware if you took the OTA, you can't Odin full versions of older software like MK2.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I got it! Thank you. Now I have kitkat so idk if I'm supposed to but that was my point in trying to root. Well anyways I tried the NC5 File and it didnt work. Then i was doing some more reading on it and realized my usb cord wasnt plugged into a USB port directly from the motherboard. It was plugged into the front USB from my case. I plugged it into the MOBO and it worked. Thanks alot!
I never got an email like I usually do when someone quotes me so sorry I couldn't respond sooner. Anyway glad to hear you got it all figured out!
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Hello fellow members.
I have an S4 SCH-I545
I feel as if I'm out of options, I have read many forums for the past 3 days and cannot find a method that works. I am currently soft bricked and cannot get ODIN to successfully flash anything. When I pull the battery and try to boot it immediately takes me to ODIN Mode, and I can't seem to get into anything but that. Just recently it has given me a new image that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I don't exactly know what it is referring to but I have Kies and there is only an emergency recover area and that does nothing.
Am I out of options? Any help is extremely appreciated.
If I left anything out let me know.
jeffysonp said:
Hello fellow members.
I have an S4 SCH-I545
I feel as if I'm out of options, I have read many forums for the past 3 days and cannot find a method that works. I am currently soft bricked and cannot get ODIN to successfully flash anything. When I pull the battery and try to boot it immediately takes me to ODIN Mode, and I can't seem to get into anything but that. Just recently it has given me a new image that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I don't exactly know what it is referring to but I have Kies and there is only an emergency recover area and that does nothing.
Am I out of options? Any help is extremely appreciated.
If I left anything out let me know.
Click to expand...
Click to collapse
What build were you on prior to this?? Jellybean...Kit Kat ?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
What build were you on prior to this?? Jellybean...Kit Kat ?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
aircooledbusses said:
Alright, I know this is not the help/question/noob thread, but I'm I'm a pickle. Redirect me if you must. Verizon s4 that was on nc5 baseband-i don't know the bootloader, but it was 4.4.2 if that helps. Rooted with towel root and twrp through too manager. Yeah, I know that's where the problem came from. So now the phone is (hopefully) in a soft brick state stuck in down load or Odin mode. Odin recognizes the phone. I don't care to keep DAT or retain root, I just was it to function. Is the nc5 full wipe with the pit my correct next step? Thank you in advance, razz me if you must, I deserve it
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Looks like me and snoopy are in the same boat, or at least our phone is in the same soft brick state. Is there any hope?
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Looks like me and snoopy are in the same boat, or at least our phone is in the same soft brick state. Is there any hope?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Absolutely there is hope. We just need to know what exact build your phones were on prior to this soft brick. Then we'd know what Odin files to give you.
Then if there were still errors you could post them here for more help.
What were you guys doing exactly that brought you to this point?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Absolutely there is hope. We just need to know what exact build your phones were on prior to this soft brick. Then we'd know what Odin files to give you.
Then if there were still errors you could post them here for more help.
What were you guys doing exactly that brought you to this point?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright sorry to make you write that again.. I just now saw you included your quote from an earlier post.
Are you able to hop onto your PC and copy and paste what the Odin error is into this thread?
Trying to flash a custom recovery on anything other than MDK will certainly lead to a soft brick most of the time. However you should be able to recover your phone back.
Using the full wipe NC5 Odin file should do it.. However if that's not working for you only those errors being posted here will allow the right people to help you along.
May seem silly but have you tried simply trying another USB cable? I've seen people on here have Odin flashes fail just due to the cable.
Grab the Odin errors though if you can
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Alright sorry to make you write that again.. I just now saw you included your quote from an earlier post.
Are you able to hop onto your PC and copy and paste what the Odin error is into this thread?
Trying to flash a custom recovery on anything other than MDK will certainly lead to a soft brick most of the time. However you should be able to recover your phone back.
Using the full wipe NC5 Odin file should do it.. However if that's not working for you only those errors being posted here will allow the right people to help you along.
May seem silly but have you tried simply trying another USB cable? I've seen people on here have Odin flashes fail just due to the cable.
Grab the Odin errors though if you can
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thank you, I'm traveling for the next few days, but will get set up with a different Samsung stock cable at my PC and report back. Knowing there is hope is a relief.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Thank you, I'm traveling for the next few days, but will get set up with a different Samsung stock cable at my PC and report back. Knowing there is hope is a relief.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There's definitely hope. If Odin can't bring you back I bet Heimdall could. It's a little more involved but obviously worth it.
Sent from my SCH-I545 using Tapatalk
Awesome! I've never used hemidal yet, but have recently been doing much better with adb commands, so I'm totally willing to learn. I'll post back here in a few days
Sent from my Nexus 7 using XDA Premium 4 mobile app
I was trying to flash Hyperdrive and ended up having to update to NC5, I can't remember what my phone was out of the box, I will be able to tell you in a few hours when I get my box. I just got the phone last week, so probably 4.3.
aircooledbusses said:
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Your firmware is mdk?....because if you not mdk you CANT use goo manger or twrp or cwm. ...you can only use safestrap....If you were mdk...and you went to nc5 you can never go back.
sent by safestrap powered echo v26
decaturbob said:
Your firmware is mdk?....because if you not mdk you CANT use goo manger or twrp or cwm. ...you can only use safestrap....If you were mdk...and you went to nc5 you can never go back.
sent by safestrap powered echo v26
Click to expand...
Click to collapse
Uh yeah I think that was my mistake. The attempt to flash twrp while on nc5 borked the phone.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Uh yeah I think that was my mistake. The attempt to flash twrp while on nc5 borked the phone.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yep..definitely the mistake
this thread and links would have helped you before you jumped off the cliff
http://forum.xda-developers.com/showthread.php?t=2606501
also odin is very touchy with using usb cables, usb ports and computers
Looks like you are trying to Odin to an image that was lower firmware than what your phone was on. You might want to try flashing the full wipe nc5 image that has been posted. I can't link to it now as I'm on my phone but if you Google Odin full wipe Verizon nc5 it should bring you to the proper xda thread to get the file.
Sent from my SCH-I545 using XDA Premium 4 mobile app
decaturbob said:
yep..definitely the mistake
this thread and links would have helped you before you jumped off the cliff
http://forum.xda-developers.com/showthread.php?t=2606501
Yep, from the thread you suggest.......... "The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases."
Sent from my GT-I9070 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
NC5 is in this thread
http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my SCH-I545 using Tapatalk
Slowbalt said:
Looks like you are trying to Odin to an image that was lower firmware than what your phone was on. You might want to try flashing the full wipe nc5 image that has been posted. I can't link to it now as I'm on my phone but if you Google Odin full wipe Verizon nc5 it should bring you to the proper xda thread to get the file.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So I followed what you said and ended up using this guide. http://forum.xda-developers.com/showthread.php?t=2735172
I did the full wipe version, and it was successful, however I still cannot boot. It will give me the samsung icon with the unlocked padlock, and then just go black, I still can boot into ODIN mode but not into recovery. Any idea what's going on?
jeffysonp said:
So I followed what you said and ended up using this guide. http://forum.xda-developers.com/showthread.php?t=2735172
I did the full wipe version, and it was successful, however I still cannot boot. It will give me the samsung icon with the unlocked padlock, and then just go black, I still can boot into ODIN mode but not into recovery. Any idea what's going on?
Click to expand...
Click to collapse
Try booting into stock recovery and do a Factory Data Reset and wipe cache then reboot.
Sent from my SCH-I545 using Tapatalk
Also once you're back to stock run Tri Angle Away to get rid of that annoying CUSTOM screen at boot lol can't stand that thing and on my phone it can make getting into CWM a pain as well.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Try booting into stock recovery and do a Factory Data Reset and wipe cache then reboot.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I can't seem to get into stock recovery either. I tried re-flashing and I still get the same results, when I try to boot into recovery I get the Samsung logo with the unlocked padlock, and then it just shuts down. :/
So I have been working on a friend of mines Verizon Note 2 (SCH-I605) and have run into an issue... I had rooted it successfully to root66 VZW stock sys, then attempted to unlock the bootloader according to the [email protected] galaxynote2root(dot)com/galaxy-note-2-tutorials/how-to-unlock-bootloader-on-verizon-galaxy-note-2-sch-i605.... without reviewing the multiplicity of comments below the article which should have caught my attention and let me know that many people were unsuccessful with that method.
So now i appear to be screwed because it will boot into ODIN but thats it. I cant even get into stock recovery. Upon boot the Galaxy Note 2 splash stays on indefinitely, as it does when i follow the instructions on this site to restore it from a failed unlock, or unroot...... ODIN 3 + sch-I605-16gb.pit + Root66-VZW-stock_sys, when it reboots following flash the splash screen stays on. I have checked the NAND erase All as suggested on this site, and it makes no difference.
When vol up/home/power is pressed it says something to the effect that 'you are a dumb*ss and have screwed up your firmware dipsh*t'....
So what now? Id hate to have to replace my buddies Note 2.... and I had absolutely 0 difficulties unlocking and rooting my HTC One, so this sucks....
Use this guide to flash back to the appropriate version.
http://forum.xda-developers.com/showthread.php?t=2024207
It's a great guide. Saved me last week after I flashed the wrong file in Odin.
Sent from my SCH-I605 using Tapatalk
michigan66 said:
Use this guide to flash back to the appropriate version.
http://forum.xda-developers.com/showthread.php?t=2024207
It's a great guide. Saved me last week after I flashed the wrong file in Odin.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
yea i did that already to no avail.... used odin to flash the pit and root66... doesnt boot...
Moridin68 said:
yea i did that already to no avail.... used odin to flash the pit and root66... doesnt boot...
Click to expand...
Click to collapse
Have you tried using a different image? What version of stock was on it before you messed with it?
Edit: If the stock version wasn't MJ9 or above then don't flash those. There currently isn't and probably won't be a way to unlock the bootloader on MJ9 and above.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
Have you tried using a different image? What version of stock was on it before you messed with it?
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
well, thats a good question... it was already in a messed up state when i got ahold of it... i tried flashing root66 and it kept failing, i checked NAND ERASE ALL and flashed CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar
as per a suggestion i read on xda.. it too failed as well, but then when i flashed root66 again (also i think with NAND ERASE on) it booted up beautifully...
Moridin68 said:
well, thats a good question... it was already in a messed up state when i got ahold of it... i tried flashing root66 and it kept failing, i checked NAND ERASE ALL and flashed CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar
as per a suggestion i read on xda.. it too failed as well, but then when i flashed root66 again (also i think with NAND ERASE on) it booted up beautifully...
Click to expand...
Click to collapse
i have recently read on a site that offers a bootloader downgrade service that if it has a knox counter, then it was updated to a version with a 'permalocked' bootloader... and if this is referring to the counter on the ODIN screen that says KNOX WARRANTY VOID:0 then this one is such a device.....
Moridin68 said:
well, thats a good question... it was already in a messed up state when i got ahold of it... i tried flashing root66 and it kept failing, i checked NAND ERASE ALL and flashed CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar
as per a suggestion i read on xda.. it too failed as well, but then when i flashed root66 again (also i think with NAND ERASE on) it booted up beautifully...
Click to expand...
Click to collapse
When you enter download mode does it say anything about Knox?
Edit: I didn't see your last post. Since it had the updated firmware with Knox, you should be at least able to get the phone working again by flashing that version of the firmware in odin. If it was on Android 4.3 then you should be able to odin MJ9 and it will work again. If it was on 4.4.2 then using odin to flash the ND7 image should fix it.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
When you enter download mode does it say anything about Knox?
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
on the download screen there is a line that says KNOX WARRANTY VOID:0
BluGuy said:
When you enter download mode does it say anything about Knox?
Edit: I didn't see your last post. Since it had the updated firmware with Knox, you should be at least able to get the phone working again by flashing that version of the firmware in odin. If it was on Android 4.3 then you should be able to odin MJ9 and it will work again. If it was on 4.4.2 then using odin to flash the ND7 image should fix it.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
he hadnt had service on that phone for several months so i guess ill try the older one first. 4.4.2.
and do i flash the pit file with those as well?
this bs is so much more tedious than working with my HTC One.
Moridin68 said:
So I have been working on a friend of mines Verizon Note 2 (SCH-I605) and have run into an issue... I had rooted it successfully to root66 VZW stock sys, then attempted to unlock the bootloader according to the [email protected] galaxynote2root(dot)com/galaxy-note-2-tutorials/how-to-unlock-bootloader-on-verizon-galaxy-note-2-sch-i605.... without reviewing the multiplicity of comments below the article which should have caught my attention and let me know that many people were unsuccessful with that method.
So now i appear to be screwed because it will boot into ODIN but thats it. I cant even get into stock recovery. Upon boot the Galaxy Note 2 splash stays on indefinitely, as it does when i follow the instructions on this site to restore it from a failed unlock, or unroot...... ODIN 3 + sch-I605-16gb.pit + Root66-VZW-stock_sys, when it reboots following flash the splash screen stays on. I have checked the NAND erase All as suggested on this site, and it makes no difference.
When vol up/home/power is pressed it says something to the effect that 'you are a dumb*ss and have screwed up your firmware dipsh*t'....
So what now? Id hate to have to replace my buddies Note 2.... and I had absolutely 0 difficulties unlocking and rooting my HTC One, so this sucks....
Click to expand...
Click to collapse
Did ID:COM turn blue in Odin? . You might have a driver problem.
doctor-cool said:
Did ID:COM turn blue in Odin? . You might have a driver problem.
Click to expand...
Click to collapse
no driver problem... it recognizes the device.... it is blue
Moridin68 said:
he hadnt had service on that phone for several months so i guess ill try the older one first. 4.4.2.
and do i flash the pit file with those as well?
this bs is so much more tedious than working with my HTC One.
Click to expand...
Click to collapse
The older one would be 4.3 which is MJ9. And yes use the pit file with it.
And just in case, I know you probably don't need it, the instructions for flashing with odin are in the return to stock section of the first post in this thread: http://forum.xda-developers.com/showthread.php?t=2024207
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
The older one would be 4.3 which is MJ9. And yes use the pit file with it.
And just in case, I know you probably don't need it, the instructions for flashing with odin are in the return to stock section of the first post in this thread: http://forum.xda-developers.com/showthread.php?t=2024207
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
right you are about 4.3 being older... i was looking through the stock roms in that very guide and saw 4.1.2 and thought that was the one you had mentioned... im downloading MJ9 now..... thanks... hope this works...
so let me ask you this, if i get it back to stock, and rooted again... even though i cant unlock the bootloader, can i get it network unlocked? this entire dilemma occurred because he wants to be able to throw a straight talk sim in this phone.
i had intended to try this www(dot)scottsroms(dot)com/showthread.php?2786-How-I-turned-my-Verizon-Note-2-into-a-World-capable-GSM-phone
once i fixed the disaster....
Moridin68 said:
right you are about 4.3 being older... i was looking through the stock roms in that very guide and saw 4.1.2 and thought that was the one you had mentioned... im downloading MJ9 now..... thanks... hope this works...
so let me ask you this, if i get it back to stock, and rooted again... even though i cant unlock the bootloader, can i get it network unlocked? this entire dilemma occurred because he wants to be able to throw a straight talk sim in this phone.
i had intended to try this www(dot)scottsroms(dot)com/showthread.php?2786-How-I-turned-my-Verizon-Note-2-into-a-World-capable-GSM-phone
once i fixed the disaster....
Click to expand...
Click to collapse
Once you get the phone working you can use Saferoot to root it, that is as long as it's working on MJ9. If the phone had been updated to ND7 which is Android 4.4.2 then there currently isn't a way to root it.
Remember even if you get root you won't be able to use a custom recovery to flash stuff.
Also the sch-i605 is already Sim unlocked from Verizon. You just have to be able to edit the apn settings.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
Once you get the phone working you can use Saferoot to root it, that is as long as it's working on MJ9. If the phone had been updated to ND7 which is Android 4.4.2 then there currently isn't a way to root it.
Remember even if you get root you won't be able to use a custom recovery to flash stuff.
Also the sch-i605 is already Sim unlocked from Verizon. You just have to be able to edit the apn settings.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok one last thing before i try this MJ9.... if it had been updated then how was i able to flash it to root66 prior to attempting to unlock the bootloader?
i really appreciate your time bro..thanks btw..
Moridin68 said:
ok one last thing before i try this MJ9.... if it had been updated then how was i able to flash it to root66 prior to attempting to unlock the bootloader?
i really appreciate your time bro..thanks btw..
Click to expand...
Click to collapse
Sorry it took so long to get back to you. I don't know a lot about root66 so I can't help you much there, but I do know that while in download mode if it says something about Knox warranty then the bootloader had been updated to a version with Knox which started with mj9 for the i605.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
Sorry it took so long to get back to you. I don't know a lot about root66 so I can't help you much there, but I do know that while in download mode if it says something about Knox warranty then the bootloader had been updated to a version with Knox which started with mj9 for the i605.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
cool then.. thanks...
BluGuy said:
Sorry it took so long to get back to you. I don't know a lot about root66 so I can't help you much there, but I do know that while in download mode if it says something about Knox warranty then the bootloader had been updated to a version with Knox which started with mj9 for the i605.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
booting up on MJ9... nicely done.
so ill check out saferoot as you said, and then edit the APN
Moridin68 said:
booting up on MJ9... nicely done.
so ill check out saferoot as you said, and then edit the APN
Click to expand...
Click to collapse
Glad it worked.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
Sorry it took so long to get back to you. I don't know a lot about root66 so I can't help you much there, but I do know that while in download mode if it says something about Knox warranty then the bootloader had been updated to a version with Knox which started with mj9 for the i605.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so now i have stock recovery menu and download menu and it boots and then hangs at the white verizon screen... i have already done a factory reset, and it still hangs.
I am unsure if I bricked my Sprint Note 3, but I tried to roo it with Chain Fire and odin, using Qbking77's YouTube video as a guide. But after the root was complete, 60% of my apps were gone, I can't using any google powered apps, and I can't go into the phones settings. Everything force closes. Honestly, I'm just trying to do a proper root so I can use Cyanogen Mod. Can someone help me revert to before I rooted,and explain the process to get cyanogen?
I followed the instructions provided, and downloaded
SM-N900P (Sprint): CF-Auto-Root-hltespr-hltespr-smn900p.zip
Followed the further stated instructions, open odin, and I cannot insert the MD5 file into odin. I was able to before, and now I cannot. Earlier I was able to do so, and as stated above, after I did it several apps disappeared, google play services no longer works,supersu is on the phone, and I cannot access the phones settings. The only thing I can do is use the stock browser. I am asking what to do/what I did wrong/how to fix it/or how to continue. If these questions cant be answered, how do I revert back to stock?
Thealbatross said:
I am unsure if I bricked my Sprint Note 3, but I tried to roo it with Chain Fire and odin, using Qbking77's YouTube video as a guide. But after the root was complete, 60% of my apps were gone, I can't using any google powered apps, and I can't go into the phones settings. Everything force closes. Honestly, I'm just trying to do a proper root so I can use Cyanogen Mod. Can someone help me revert to before I rooted,and explain the process to get cyanogen?
I followed the instructions provided, and downloaded
SM-N900P (Sprint): CF-Auto-Root-hltespr-hltespr-smn900p.zip
Followed the further stated instructions, open odin, and I cannot insert the MD5 file into odin. I was able to before, and now I cannot. Earlier I was able to do so, and as stated above, after I did it several apps disappeared, google play services no longer works,supersu is on the phone, and I cannot access the phones settings. The only thing I can do is use the stock browser. I am asking what to do/what I did wrong/how to fix it/or how to continue. If these questions cant be answered, how do I revert back to stock?
Click to expand...
Click to collapse
I would Odin back to nk4, then do the ota, and then instead of all the cf stuff I would just odin twrp and flash supersu. It's literally that simple.
Sent from my SM-N900P using XDA Free mobile app
How do I do these things?
Thealbatross said:
How do I do these things?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=60272319
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
http://forum.xda-developers.com/showthread.php?p=60272319
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
The TWRP file in that post downloads as .img, and when I change it to .tar it becomes unusable and odin marks it as a fail. This has been the issue for me throughout this entire root process. People to me "Download this" and it either
1. Doesn't work
2. Gets to 100% extraction then fails
3. Odin wont let me insert the file.
I know its not me doing anything wrong. Right now, my phone boots to the sprint logo, and nothing past it. I can go into download mode and that's about it. I just need help and the proper instructions to either put it back to stock, or do a proper root. I rooted a Galaxy S2 years ago, and several other phones between now and then, and got it on the first try. This process with the Note 3 has been very frustrating, and I've been without my phone for 4 days. So if you, or anyone else knows the DETAILED steps I need to take, please help.
I did what you said with the NK4 thing, and like I said above, it would get to 100% extraction then fail. I got it from the sammobile site, and they wouldnt even let me redownload it. And I dont know what OTA is.
Thealbatross said:
The TWRP file in that post downloads as .img, and when I change it to .tar it becomes unusable and odin marks it as a fail. This has been the issue for me throughout this entire root process. People to me "Download this" and it either
1. Doesn't work
2. Gets to 100% extraction then fails
3. Odin wont let me insert the file.
I know its not me doing anything wrong. Right now, my phone boots to the sprint logo, and nothing past it. I can go into download mode and that's about it. I just need help and the proper instructions to either put it back to stock, or do a proper root. I rooted a Galaxy S2 years ago, and several other phones between now and then, and got it on the first try. This process with the Note 3 has been very frustrating, and I've been without my phone for 4 days. So if you, or anyone else knows the DETAILED steps I need to take, please help.
I did what you said with the NK4 thing, and like I said above, it would get to 100% extraction then fail. I got it from the sammobile site, and they wouldnt even let me redownload it. And I dont know what OTA is.
Click to expand...
Click to collapse
If you're not getting a boot then you need to restart.
1)Get the tar for nk4.
2)Odin the nk4 (but get to download mode by pulling the battery then boot to download mode).
3) After a successful odin of nk4, you should be official. If not, boot to recovery, wipe data, then odin again (battery pull)
4) If going to oc5, take the ota. Or go to next step.
5) after ota (or not) now we root. Provided you don't care about knox, the best way is to get the twrp img from their site. Flash that with odin (battery pull).
6) download a supersu.zip to flash from twrp, and flash it.
I can't link these files right now, but it's easy to find them. If you need links later, I can help in an hour or so.
And ota is over the air, when you get a notification for an update
Sent from my SM-N900P using XDA
Ok, thanks, Ill wait for the file links.
Thealbatross said:
Ok, thanks, Ill wait for the file links.
Click to expand...
Click to collapse
Nk4 tar: http://forum.xda-developers.com/showthread.php?p=47355107
Twrp link to sprint note 3, pay attention to the odin instructions: http://twrp.me/devices/samsunggalaxynote3sprint.html
SuperSU: https://docs.google.com/file/d/0B8umY4TqG8CVamo0amUtQ3hKNXc/edit?usp=docslist_api
There ya go.
Sent from my SM-N900P using XDA Free mobile app
I can very thankfully say that md5 file downloaded and is installing without a problem.
now, the TWRP site you gave me, I can use the most recent version, correct?
EDIT: Both NK4 and TWRP are installed but still cant get by sprint logo. Is this normal?
Thealbatross said:
I can very thankfully say that md5 file downloaded and is installing without a problem.
now, the TWRP site you gave me, I can use the most recent version, correct?
Click to expand...
Click to collapse
Yes.
Link post updated for supersu
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
If you're not getting a boot then you need to restart.
1)Get the tar for nk4.
2)Odin the nk4 (but get to download mode by pulling the battery then boot to download mode).
3) After a successful odin of nk4, you should be official. If not, boot to recovery, wipe data, then odin again (battery pull)
4) If going to oc5, take the ota. Or go to next step.
5) after ota (or not) now we root. Provided you don't care about knox, the best way is to get the twrp img from their site. Flash that with odin (battery pull).
6) download a supersu.zip to flash from twrp, and flash it.
I can't link these files right now, but it's easy to find them. If you need links later, I can help in an hour or so.
And ota is over the air, when you get a notification for an update
Sent from my SM-N900P using XDA
Click to expand...
Click to collapse
So steps 2 and 3 worked, but I still get stuck at the sprint logo.
Actually, ignore everything stated above, Im back to stock with custom recovery. What's Next?
Thealbatross said:
So steps 2 and 3 worked, but I still get stuck at the sprint logo.
Click to expand...
Click to collapse
Boot to recovery, wipe data, and try booting. If that didn't do out, wipe data again then pull battery, boot to download mode, and odin nk4 again. Those files are the ones I have used so...yeah...lol.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
Boot to recovery, wipe data, and try booting. If that didn't do out, wipe data again then pull battery, boot to download mode, and odin nk4 again. Those files are the ones I have used so...yeah...lol.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Its good to go now, look above lol
Thealbatross said:
Actually, ignore everything stated above, Im back to stock with custom recovery. What's Next?
Click to expand...
Click to collapse
Well, if you have custom recovery and don't want ota, flash supersu.
If you want ota you gotta redo the nk4 steps and then take ota, but do not install twrp once you odin
Sent from my SM-N900P using XDA Free mobile app
Do I need it? Im not even sure what it and oc5 are.
Thealbatross said:
Do I need it? Im not even sure what it and oc5 are.
Click to expand...
Click to collapse
Oc5 is lollipop. Major upgrade to Android. However, many things, like xposed, aren't working yet. Your call man.
Sent from my SM-N900P using XDA Free mobile app
Well, ota sounds like it will be helpful. And the version of Cyanogen I want required lollipop. So walk through me through I guess. Everything has gone well so far haha
jlechner said:
Oc5 is lollipop. Major upgrade to Android. However, many things, like xposed, aren't working yet. Your call man.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Actually, ill just move on without them. I dont want to mess up my current progress.
Thealbatross said:
Actually, ill just move on without them. I dont want to mess up my current progress.
Click to expand...
Click to collapse
Ha! It's all in learning man. That and finding downloads. If you decide you want ota, just re-odin nk4 (after a factory reset, and use battery pull for download mode), take the ota, re-odin twrp, reboot to twrp and flash supersu.zip. Pretty easy.
Sent from my SM-N900P using XDA Free mobile app