I just tried to upgrade to Alliance build 30 from build 26. I also loaded TWRP latest version after using CWM for a few years now. I had no idea CWM files would not restore with TWRP. Yes I was stupid but now I cannot install anything or get out of recovery having no working recovery file in TWRP. Do I have to start over with Odin? Can I somehow get back to CWM recovery files and bypass TWRP? I see my counter does not show any custom files and is still at zero. Please help me!
NB2A said:
I just tried to upgrade to Alliance build 30 from build 26. I also loaded TWRP latest version after using CWM for a few years now. I had no idea CWM files would not restore with TWRP. Yes I was stupid but now I cannot install anything or get out of recovery having no working recovery file in TWRP. Do I have to start over with Odin? Can I somehow get back to CWM recovery files and bypass TWRP? I see my counter does not show any custom files and is still at zero. Please help me!
Click to expand...
Click to collapse
When you are in twrp have you tried flashing the cwm recovery zip to switch back yo cwm?
bigmarv31 said:
When you are in twrp have you tried flashing the cwm recovery zip to switch back yo cwm?
Click to expand...
Click to collapse
Yes I did try that too. I was finally able to get Alliance rom to load but it gets stuck at logo never completing. In fact now it put into yellow triangle saying return to Verizon store so even Odin cannot see it.
Thank you for helping anyway
Did you put phone in download mode then try to use odin
I just put it in Odin mode
I guess I need to start all over again
Should I use Adam's thread?
bigmarv31 said:
Did you put phone in download mode then try to use odin
Click to expand...
Click to collapse
where you on stock 4.1.2?
If you were on stock 4.1.2 use odin with the proper files then you can use Adams Casual No You Verizon.
bigmarv31 said:
where you on stock 4.1.2?
If you were on stock 4.1.2 use odin with the proper files then you can use Adams Casual No You Verizon.
Click to expand...
Click to collapse
NB2A said:
Thank you for responding with such detail. It finally started to boot into Alliance logo but never completed. Now it says with yellow triangle phone needs to be returned to Verizon. It does not even work in Odin. I do have an external reader for the card but I guess I am screwed now anyway.I wonder if Verizon will even help me at all back to stock.
Click to expand...
Click to collapse
@NB2A - I see where you have 2 threads on this.... so I'm just going to respond in this thread to avoid confusion.
If you can get into download mode again with Volume Down+Home+Power button combo.... then you should be able to use ODIN to restore the phone to whatever firmware version would be appropriate. Like bigmarv31 said, you should be able to restore back to 4.1.2 as long as you never installed factory stock 4.3 or 4.4.2. If you did install 4.3 or 4.4.2, then your bootloader has been locked and you would have to restore back to one of those firmwares and can't go back to 4.1.2 because of locked bootloader. (I had assumed you were still on 4.1.2 bootloader because you said you had TWRP CWM on the phone). If you can't get into download mode, then do a Google search for tricks to force phone into download mode. I've read where people say you can pull the battery and plug in the phone... or use a special usb jig to get the phone into download mode if the button combo doesn't work anymore. These tricks aren't guaranteed to work, but would be worth a shot.
You can buy a usb jig from eBay for less than $5. (This may be a good one: http://www.ebay.com/itm/MICRO-USB-J...er_Cell_Phone_Accessories&hash=item1e6d6cc865).
Good luck.
PS: If you can get the phone into download mode again, use section 1b of Droidstyle's restore guide to restore the phone ( http://forum.xda-developers.com/showthread.php?p=34891181).
Thank you again
I was able to finally get phone to work using Odin. Now I need to root it and since it is using a 4.3 build My options are only touch wiz apps I am told and can only use safestrap to use another rom. I would be happy to simply be back on what I had working fine in it before this yesterday. I had Beanstown build 26 before Alliance build 30 messed me up. I cannot seem to find root to use now.
Thank you again
mattnmag said:
@NB2A - I see where you have 2 threads on this.... so I'm just going to respond in this thread to avoid confusion.
If you can get into download mode again with Volume Down+Home+Power button combo.... then you should be able to use ODIN to restore the phone to whatever firmware version would be appropriate. Like bigmarv31 said, you should be able to restore back to 4.1.2 as long as you never installed factory stock 4.3 or 4.4.2. If you did install 4.3 or 4.4.2, then your bootloader has been locked and you would have to restore back to one of those firmwares and can't go back to 4.1.2 because of locked bootloader. (I had assumed you were still on 4.1.2 bootloader because you said you had TWRP on the phone). If you can't get into download mode, then do a Google search for tricks to force phone into download mode. I've read where people say you can pull the battery and plug in the phone... or use a special usb jig to get the phone into download mode if the button combo doesn't work anymore. These tricks aren't guaranteed to work, but would be worth a shot.
You can buy a usb jig from eBay for less than $5. (This may be a good one: http://www.ebay.com/itm/MICRO-USB-J...er_Cell_Phone_Accessories&hash=item1e6d6cc865).
Good luck.
PS: If you can get the phone into download mode again, use section 1b of Droidstyle's restore guide to restore the phone ( http://forum.xda-developers.com/showthread.php?p=34891181).
Click to expand...
Click to collapse
NB2A said:
I was able to finally get phone to work using Odin. Now I need to root it and since it is using a 4.3 build My options are only touch wiz apps I am told and can only use safestrap to use another rom. I would be happy to simply be back on what I had working fine in it before this yesterday. I had Beanstown build 26 before Alliance build 30 messed me up. I cannot seem to find root to use now.
Thank you again
Click to expand...
Click to collapse
Cool. Glad you got it restored. If you're on factory stock 4.3, then you can use safeRoot to gain root access. Here's the link to saferoot-- http://forum.xda-developers.com/showthread.php?p=48392009.
---------- Post added at 01:05 PM ---------- Previous post was at 01:00 PM ----------
Oh... and you probably know, but you need to use the modified TWRP called Safestrap in order to run Alliance 26 again.
mattnmag said:
Cool. Glad you got it restored. If you're on factory stock 4.3, then you can use safeRoot to gain root access. Here's the link to saferoot-- http://forum.xda-developers.com/showthread.php?p=48392009.
---------- Post added at 01:05 PM ---------- Previous post was at 01:00 PM ----------
Oh... and you probably know, but you need to use the modified TWRP called Safestrap in order to run Alliance 26 again.
Click to expand...
Click to collapse
This looks like a real PIA to root. Thank you so much.
Saferoot
NB2A said:
This looks like a real PIA to root. Thank you so much.
Click to expand...
Click to collapse
I unzipped that file on that thread and there does not seem to be any install bat file to use for step 5.
NB2A said:
I unzipped that file on that thread and there does not seem to be any install bat file to use for step 5.
Click to expand...
Click to collapse
This rooting process is actually very easy. I just downloaded and unzipped the saferoot zip package, and the batch file is definitely there. (see the below screenshot) It's not named "install.bat" -- just "install" (but you can see which one is the batch file).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mattnmag said:
This rooting process is actually very easy. I just downloaded and unzipped the saferoot zip package, and the batch file is definitely there. (see the below screenshot) It's not named "install.bat" -- just "install" (but you can see which one is the batch file).
Click to expand...
Click to collapse
No matter what either saferoot or safestrap does not seem my phone
The drivers are there too when I plug phone
NB2A said:
No matter what either saferoot or safestrap does not seem my phone
The drivers are there too when I plug phone
Click to expand...
Click to collapse
I'm sorry, but I don't really understand what you mean. You mean when you followed all the steps in the saferoot thread, and double clicked on the install batch file.... that the saferoot install script could not see your phone? Did you make sure to enable usb debugging in the developer settings on your phone? When you connect your phone to your computer with the usb cable, open a command terminal screen... then type "adb devices" (without the quotes) into the terminal... does it show your phone's serial number to ensure your phone is being seen by the computer? If not, you probably need to install the stand alone Android SDK tools from here:
( https://developer.android.com/sdk/index.html#Other ).
Also.... I don't understand what safeStrap would have to do with this. SafeStrap is a modified version of TWRP that you would install onto your phone only after you get the phone rooted with safeRoot. You would need to use SafeStrap as the recovery now because the bootloader was locked permanently after you put factory stock 4.3 on the phone... and regular TWRP and CWM won't work with locked bootloaders. After you get Safestrap on there, you would boot into it to flash the Alliance 26 ROM back onto the phone. You'll need to research in the Safestrap thread for the steps, as I am actually still on 4.1.2 bootloader and don't need to use Safestrap.... so I've never used it. As I recall though, you need to make a full backup of your stock ROM first (also backup the efs if you haven't already). Then you have to flash the custom ROM over the stock ROM slot in Safestrap. Here's a link for the Safestrap thread for your reading pleasure : http://forum.xda-developers.com/showthread.php?t=2704992
PS: I see where you're posting in the Alliance Build 30 thread for help. To avoid confusion, make sure they know you're on factory stock 4.3 and your trying to root and install Alliance 30 (which is based on Android version 4.4.2). You're going to end up soft bricking the phone again if you try to install Alliance 30 in SafeStrap with stock 4.3. Alliance 30 is based on 4.4.2 and uses a different kernel than Alliance 26 (which is 4.3 based).
I appreciate your help. One major unexplained problem I had was safestrap or saferoot could not see my device at all using a machine with XP. After switching to a machine with windows 7 both worked and saw device fine. I am now running Beans build 26 and used Safestrap as well. I now ned to make a recovery copy of 26. I did make a copy of the working stock room too just in case. I just need to determine what is the best place to save it off the device too.
NB2A said:
I appreciate your help. One major unexplained problem I had was safestrap or saferoot could not see my device at all using a machine with XP. After switching to a machine with windows 7 both worked and saw device fine. I am now running Beans build 26 and used Safestrap as well. I now ned to make a recovery copy of 26. I did make a copy of the working stock room too just in case. I just need to determine what is the best place to save it off the device too.
Click to expand...
Click to collapse
Save them to your sd card and if u want copy them to your computer just in case you ever need them.
mattnmag said:
PS: I see where you're posting in the Alliance Build 30 thread for help. To avoid confusion, make sure they know you're on factory stock 4.3 and your trying to root and install Alliance 30 (which is based on Android version 4.4.2). You're going to end up soft bricking the phone again if you try to install Alliance 30 in SafeStrap with stock 4.3. Alliance 30 is based on 4.4.2 and uses a different kernel than Alliance 26 (which is 4.3 based).
Click to expand...
Click to collapse
I was one of the guys trying to help over there. It was confusing to say the least. There was never any mention of whether the bootloader was unlocked or not. I assumed it was and made suggestions based on that premise. I'm sorry I didn't ask for more detail before I did.
If I had known it was locked I would have never said a word. I know nothing about SafeStrap. I've been on the unlocked VRALJB Bootloader ever since I've had my phone. Sorry I stuck my nose in where it didn't belong.
Sent from my SCH-I605 using XDA Free mobile app
Related
I was originally trying to just go to the new kitkat rom, i believe that was CM11 or something of the sort. But for some reason i cannot do anything with my phone when it comes to installing or changing the recovery. Odin fails every time. One-Click-Root fails every time (which i think is what i used from the beginning to root). I even upgraded ROM manager to pro so i could try the touch based recovery and it will not successfully install a recovery that i can boot into even though it says that it has and shows(ed) the current recovery being the most up-to-date version. And now since ive tried several different today, i have lost root somehow...even thought i just had it and didnt change anything with the root process...just trying to regain even the stock recovery. Basically what happens if i try to boot into recovery mode is it tries for half a second then boots to ODIN mode and in the top left corner it says failed normal boot or something of the sort.
Can someone point me in the right direction? would a factory reset within the android OS help anything? every thing is backed up, so that wont be an issue as far as apps/data and important files goes.
The phone still boots to my "rooted" 4.3 that i have installed, just dont have root privelages any longer...the phone still works as normal...just cant do anything root based...like run titanium backup or supersu, and even ROM manager is NOW giving me an error when trying to install a custom recovery.
I would like to restore to stock MDK so i can start from scratch and install the CM11 KitKat Rom if at all possible...
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
decaturbob said:
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
Click to expand...
Click to collapse
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
MURD3RD said:
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
Click to expand...
Click to collapse
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
decaturbob said:
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
Click to expand...
Click to collapse
you got a link to a good working Loki tutorial?
Here's a link to the stock mdk tar file. This will totally wipe your phone. http://www.sxtpdevelopers.com/showthread.php?t=237
Ryno77 said:
Here's a link to the stock mdk tar file. This will totally wipe your phone.
Click to expand...
Click to collapse
i did find that link before and am currently downloading it...but it is taking forever...everything else i download is blazing fast (50Mb D/L speed here at my buddies apartment) but yet this file is only downloading at 50KB/s...and is showing over 9-10 hours for the download to be complete...does anybody have a faster download source?
i know my connection is phenomenal since i downloaded a 9 gig file last night from a different source and it took under an hour...this .tar is less than 2 gigs...shouldnt take that damn long...
i also tried flashing the recovery .tar.md5 from that link...same exact result...
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
kennyglass123 said:
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
Click to expand...
Click to collapse
THANKS!!!
I knew i hadn't put it in the right place...hopefully it'll get more view here...and i can get this thing sorted out
so right now the screen shows (phone)--(yellow triangle)--(computer) and says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
this is after trying to install the stock restore .tar files in the link mentioned above...the device will NO LONGER boot the os and goes to this screen every time. I can still get it into download (Odin) mode though.
MURD3RD said:
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
Click to expand...
Click to collapse
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
k1mu said:
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
Click to expand...
Click to collapse
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
MURD3RD said:
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
Click to expand...
Click to collapse
You won't be on MDK, so no KitKat.
k1mu said:
You won't be on MDK, so no KitKat.
Click to expand...
Click to collapse
but i have had no problem flashing back to get rooted when i first got the device...even though several threads said it couldnt be done...all i need is to get back to stock and start from scratch...at least i hope this is the case. If it goes ahead and installs the newest 4.3 update...and i truly cant change it due to no exploits yet...then i guess ill have to wait...lol, it could be worse, haha
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
MURD3RD said:
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
Click to expand...
Click to collapse
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
EDIT: well nevermind...i think i was just crazy to think something different...i am definitely running the latest release of 4.3 from vzw...fml...well at least it can still be rooted. Is there any development for KitKat on the new MK2 software? Ill do some searching around...
i do remember, however, doing something that a tutorial said specifically not to do...and it worked anyway...even though several people responding to the thread said not to do or it would brick the phone...o well i guess...if i find the link ill post it up...
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
would you happen to have a link to the safestrap tutorial? i cant seem to locate it...im gunna do some more searching, but if you had a link at the ready, that'd be awesome!!!
EDIT: Found it...no worries
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
so i found the thread for this ROM and it doesnt say anything about being able to run on MK2 build...can anyone shed some light on this? it only says MJ7...
Check out these images of my downloader before and after I updated to 4.4.4 does yours look like this ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The image on the right with the blue lettering is after the update. Notice the change in text for the KNOX WARRANTY and KNOX KERNEL LOCK is missing. I want back to 4.4.2 twice and got the same results. The first time I attempted to go back to 4.4.2 from 4.4.4 it boot looped on the restart. I was wondering if anybody has tried to go back, and had this problem? I finally got 4.4.2 to stick, but it wasn't easy.
download mode
jimzweb1 said:
Check out these images of my downloader before and after I updated to 4.4.4 does yours look like this ?
The image on the right with the blue lettering is after the update. Notice the change in text for the KNOX WARRANTY and KNOX KERNEL LOCK is missing. I want back to 4.4.2 twice and got the same results. The first time I attempted to go back to 4.4.2 from 4.4.4 it boot looped on the restart. I was wondering if anybody has tried to go back, and had this problem? I finally got 4.4.2 to stick, but it wasn't easy.
Click to expand...
Click to collapse
i am still stuck at boot looped looking at sprint 4g logo, flash back to nc5 from 4.4.4 now i am stuck please help, this is my fourth time of flashing the stock rom 4.4.2 and still stuck
aliabkad said:
i am still stuck at boot load flash back to nc5 from 4.4.4 now i am stuck please help
Click to expand...
Click to collapse
I definitely understand, I was there yesterday !!! This is how I fixed it. I am going to assume you know how to hold the buttons to get into the modes. First, pull the battery then reinsert. Now go to download mode, and reflash the recovery that you where using with 4.4.2 i.e. CWM or TWRP. Now pull the battery then reinsert. Go to the recovery you installed, and wipe the ROM, CACHE, and DELVIK CACHE just like you where going to install new ROM. Use the recovery to boot into download mode or pull the battery and reinstall, and go to download mode. Install drivers on PC and use Odin version 1.85 here is the link http://www.downloadodin.info/download-odin-1-85 flash a fresh copy of NC5 4.4.2 here is the link http://forum.xda-developers.com/showthread.php?t=2712205 this will get you back to 4.4.2, which is where I'm going to stay till they get some of the bugs out. Never could get CWM recovery to stick after updated to 4.4.4, let me know how it goes.
aliabkad said:
i am still stuck at boot looped looking at sprint 4g logo, flash back to nc5 from 4.4.4 now i am stuck please help, this is my fourth time of flashing the stock rom 4.4.2 and still stuck
Click to expand...
Click to collapse
Man, that sounds familiar I did the same thing. After the fourth attempt I realized the baseband or bootloader was corrupt. So I used kind of the back door to go in and WIPE everything, and start over.
jimzweb1 said:
I definitely understand, I was there yesterday !!! This is how I fixed it. I am going to assume you know how to hold the buttons to get into the modes. First, pull the battery then reinsert. Now go to download mode, and reflash the recovery that you where using with 4.4.2 i.e. CWM or TWRP. Now pull the battery then reinsert. Go to the recovery you installed, and wipe the ROM, CACHE, and DELVIK CACHE just like you where going to install new ROM. Use the recovery to boot into download mode or pull the battery and reinstall, and go to download mode. Install drivers on PC and use Odin version 1.85 here is the link http://www.downloadodin.info/download-odin-1-85 flash a fresh copy of NC5 4.4.2 here is the link http://forum.xda-developers.com/showthread.php?t=2712205 this will get you back to 4.4.2, which is where I'm going to stay till they get some of the bugs out. Never could get CWM recovery to stick after updated to 4.4.4, let me know how it goes.
Click to expand...
Click to collapse
i odin flash stock nc5 4.4.2 now am stock at sprint logo
aliabkad said:
i odin flash stock nc5 4.4.2 now am stock at sprint logo
Click to expand...
Click to collapse
Ok, you did use Odin to reinstall the original recovery that you had before you updated to 4.4.4 correct ? Which recovery did you install ? Did you WIPE the ROM, wiping just the cache and delvik cache won't do it. You need to wipe everything. Go through the process again to make sure everything sticks. Also remember it will take a few minutes on the first boot just like it did when the phone was new.
jimzweb1 said:
Ok, you did use Odin to reinstall the original recovery that you had before you updated to 4.4.4 correct ? Which recovery did you install ? Did you WIPE the ROM, wiping just the cache and delvik cache won't do it. You need to wipe everything. Go through the process again to make sure everything sticks. Also remember it will take a few minutes on the first boot just like it did when the phone was new.
Click to expand...
Click to collapse
i first odin flash NC5_OEM_BL.tar.md5 and then odin flash the stock rom i know at this point i no longer have root , booted to sprint logo that is where am at right now waiting for miracles. if i can get new 4.4.4. stock rom to odin i will be fine
---------- Post added at 02:47 PM ---------- Previous post was at 02:36 PM ----------
aliabkad said:
i first odin flash NC5_OEM_BL.tar.md5 and then odin flash the stock rom i know at this point i no longer have root , booted to sprint logo that is where am at right now waiting for miracles. if i can get new 4.4.4. stock rom to odin i will be fine
Click to expand...
Click to collapse
finally got it to work, i just power+home+volume up took me to the stock recovery then i did a factory reset, voila.Thank you jimzweb1, i was in the panic mode again thank you for bringing me back to life, you rock !!!!. peace.
aliabkad said:
i first odin flash NC5_OEM_BL.tar.md5 and then odin flash the stock rom i know at this point i no longer have root , booted to sprint logo that is where am at right now waiting for miracles. if i can get new 4.4.4. stock rom to odin i will be fine
Click to expand...
Click to collapse
I am not familiar with NC5_OEM_BL.tar.md5 you are using. If you are trying to keep the sprint logo you can always change the CSC code. Don't worry about trying to match md5's. Just try and use the links I gave you, the instructions are in the NC5 thread on the how to change the zip into a tar file and Odin will match md5's during the NC5 install. Let me know how its going.
aliabkad said:
i first odin flash NC5_OEM_BL.tar.md5 and then odin flash the stock rom i know at this point i no longer have root , booted to sprint logo that is where am at right now waiting for miracles. if i can get new 4.4.4. stock rom to odin i will be fine
---------- Post added at 02:47 PM ---------- Previous post was at 02:36 PM ----------
finally got it to work, i just power+home+volume up took me to the stock recovery then i did a factory reset, voila.Thank you jimzweb1, i was in the panic mode again thank you for bringing me back to life, you rock !!!!. peace.
Click to expand...
Click to collapse
Awesome !!! I know what that panic mode is like.
aliabkad said:
i odin flash stock nc5 4.4.2 now am stock at sprint logo
Click to expand...
Click to collapse
Did you trip your knox count doing this downgrade
No only when i first rooted 4.4.4 then tripping knox counts
Sent from my SM-N900P using XDA Free mobile app
Guys make sure when using Odin, that you are using a good, usb cord .. Use thr one that came with the phone if you can, or its equal.. DO NOT USE any of those cheepies from the corner store.. They will ruin your day...
Very helpful info. Thx..
caleb2014 said:
Very helpful info. Thx..
Click to expand...
Click to collapse
Thanks, don't see where a flash counter (KNOX) has anything to do with the (KNOX) program which secures data with an encrypted container to send to another location ? So, the most likely explanation is Samsung and the NSA are just gathering a little info for personal use !!! Lol
JimWebz,
Ironically I came across your post. I tried to go from NH7 to NC5 and was stuck in the treacherous bootloop, whoo it was scary especially for a N00B, but I had enough sense to go to my previous posts that you and others have commented on to find Micmars completely stock NH7, followed his instructions and voila! Back in buisness, now forget using Towelroot, going back to NC5 was the biggest pain, and damn near scary! Chainfire here I come!!!!
TheNewGuy14 said:
JimWebz,
Ironically I came across your post. I tried to go from NH7 to NC5 and was stuck in the treacherous bootloop, whoo it was scary especially for a N00B, but I had enough sense to go to my previous posts that you and others have commented on to find Micmars completely stock NH7, followed his instructions and voila! Back in buisness, now forget using Towelroot, going back to NC5 was the biggest pain, and damn near scary! Chainfire here I come!!!!
Click to expand...
Click to collapse
Yes it happens a lot. Going back to NC5 usually ends up in a bootloop, it did for me. The easiest way out of it, is to pull the battery and boot into recovery. If you have a stock recovery the do a factory reset. Then check and see what version of KiKat your on ( i.e. did you make back to NC5 or are you still on NH7 ). If your still on Nh7 use odin to flash again it should take the second time. OR, if you still have a custom recovery then wipe your entire OS, cache, and delvik cache as if you are going to install a new rom. Then power down device completely then boot into download mode and odin flash NC5 again and it take now.
I run Stock Rooted 4.4.2 NC5 with Philz custom CWM version 6.12.9 hltespr. I ran NH7 4.4.4 rooted for about a week, I didn't have any major problems but a lot of other people where. So went back to NC5 which for me has always been rock solid.
Hey Jimwebz,
I have a question, saw this minor detail and wonder if it's the cause of bootlooping. The official Sprint build is N900PVPUDNC5 while the one's on XDA available from those posts are N900PVPUCNC5 PUC instead of PUD. Is there a difference?
Thanks man!
TheNewGuy14 said:
Hey Jimwebz,
I have a question, saw this minor detail and wonder if it's the cause of bootlooping. The official Sprint build is N900PVPUDNC5 while the one's on XDA available from those posts are N900PVPUCNC5 PUC instead of PUD. Is there a difference?
Thanks man!
Click to expand...
Click to collapse
Near as I can figure it's a typo ? Should be N900PVPUCNC5 which is 4.4.2 NC5, and it should be N900PVPUDNH7 which is 4.4.4 NH7. I wish it was the cause, but idone says the cause is not letting the device finish a full install including the stock recovery. I'm not sure, but going back is just a bootloop and it is easy to correct. So I am going to hang out on NC5 it is still a rock solid base for a daily driver, then I can mess around with roms like Priest Punch and some of the cool themes that have come out !!!
I want to revert an ATT i717 rooted, with CWM ver.6, custom KK rom back to ATT stock rom (I did try KIES but it didn't recognize phone as I understand due to rom being custom.) I don't have a back up of the original stock rom. All download links I have come across are dead. Need help to locate working DL links.
2-Wifey has the same exact phone rooted with CWM ver. 6 with stock JB rom. I am wondering if I take a back up of that and flash it to my phone if that will be ok or if that's a chance for a brick?
jayinc11 said:
I want to revert an ATT i717 rooted, with CWM ver.6, custom KK rom back to ATT stock rom (I did try KIES but it didn't recognize phone as I understand due to rom being custom.) I don't have a back up of the original stock rom. All download links I have come across are dead. Need help to locate working DL links.
2-Wifey has the same exact phone rooted with CWM ver. 6 with stock JB rom. I am wondering if I take a back up of that and flash it to my phone if that will be ok or if that's a chance for a brick?
Click to expand...
Click to collapse
You have posted in the development forum. Try Q&A.
Also if you can't find Odin file here, try to search google. You may find an active somewhere else. Other than that, you can wait. if I ever get off work I could probably scrounge up a copy to my dropbox.
Let me know if you find. Sorry, I won't have time until tomorrow afternoon . In middle of a work marathon on 2 jobs.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
jayinc11 said:
I want to revert an ATT i717 rooted, with CWM ver.6, custom KK rom back to ATT stock rom (I did try KIES but it didn't recognize phone as I understand due to rom being custom.) I don't have a back up of the original stock rom. All download links I have come across are dead. Need help to locate working DL links.
2-Wifey has the same exact phone rooted with CWM ver. 6 with stock JB rom. I am wondering if I take a back up of that and flash it to my phone if that will be ok or if that's a chance for a brick?
Click to expand...
Click to collapse
here's a link to stock jb:
https://drive.google.com/file/d/0B8CfFE5fSiMQS1NuZVZmUnRNYVU/view?usp=sharing
it includes the rom, cwm recovery, supersu, odin, kernel, and modem.
odin the rom first, then the recovery.
copy supersu to the phone and install thru cwm.
you'll need to update binaries.
also included is the current cwm recovery i use to install kit kat roms.
beenkenobee said:
here's a link to stock jb:
https://drive.google.com/file/d/0B8CfFE5fSiMQS1NuZVZmUnRNYVU/view?usp=sharing
it includes the rom, cwm recovery, supersu, odin, kernel, and modem.
odin the rom first, then the recovery.
copy supersu to the phone and install thru cwm.
you'll need to update binaries.
also included is the current cwm recovery i use to install kit kat roms.
Click to expand...
Click to collapse
Hey thanx! Just a quick question - what is to update binaries and how do I go about that?
captemo said:
You have posted in the development forum. Try Q&A.
Also if you can't find Odin file here, try to search google. You may find an active somewhere else. Other than that, you can wait. if I ever get off work I could probably scrounge up a copy to my dropbox.
Let me know if you find. Sorry, I won't have time until tomorrow afternoon . In middle of a work marathon on 2 jobs.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Hey thanx - I am following the d/l link from above. Unless otherwise think it will work out.
jayinc11 said:
Hey thanx! Just a quick question - what is to update binaries and how do I go about that?
Click to expand...
Click to collapse
once you get done installing and the phone booted up,
start supersu and follow the instructions.
beenkenobee said:
once you get done installing and the phone booted up,
start supersu and follow the instructions.
Click to expand...
Click to collapse
Finally d/l at work, odined the rom and encountered "Firmware upgrade encountered an issue, Please select recovery mode in kies and try again"
Phone cannot enter recov. mode nor download mode. I tried kies and 2 issues came up 1 my phone has no serial number, I entered wife's S/No. (same exact phone, both made in Korea) but the second problem is that kies wants me to turn off phone, and enter d/l mode which isn't coming up.
I tried my JIG thingy but same screen comes up.
How do I fix this?
ATTN: MOD
If need be please move thread as appropriate.
jayinc11 said:
Finally d/l at work, odined the rom and encountered "Firmware upgrade encountered an issue, Please select recovery mode in kies and try again"
Phone cannot enter recov. mode nor download mode. I tried kies and 2 issues came up 1 my phone has no serial number, I entered wife's S/No. (same exact phone, both made in Korea) but the second problem is that kies wants me to turn off phone, and enter d/l mode which isn't coming up.
I tried my JIG thingy but same screen comes up.
How do I fix this?
ATTN: MOD
If need be please move thread as appropriate.
Click to expand...
Click to collapse
i've restored using this many many times and never ran into a problem.
did you odin only the firmware tar?
possibly a bad d/l.
See below
beenkenobee said:
i've restored using this many many times and never ran into a problem.
did you odin only the firmware tar?
possibly a bad d/l.
Click to expand...
Click to collapse
Could be, really don't know for sure. Note has this screen. Anything I attempt it's resulting in the following screen below. DL mode, hit volume up and bam, same screen. Recovery, same deal, try to boot normally = same. Even a jig gets the DL mode first screen and then bam! Is there any way to fix this or Is the phone at the point of jtag repair, or worse a brick?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jayinc11 said:
Could be, really don't know for sure. Note has this screen. Anything I attempt it's resulting in the following screen below. DL mode, hit volume up and bam, same screen. Recovery, same deal, try to boot normally = same. Even a jig gets the DL mode first screen and then bam! Is there any way to fix this or Is the phone at the point of jtag repair, or worse a brick?
Click to expand...
Click to collapse
uninstall kies.
reinstall the usb driver if needed and try again.
I went to upgrade to the new hyperdrive since they sent me the ota. Phone has been acting weird so I was going to do a complete wipe. I took my sd card out which my son took and lost on me and OI can find anywhere. I had another card so d/l new hyperdrive onto other card. I went to wipe cache and install new rom. phone wiped data and now wouldnt install new rom. I dont remember all the build I was on on the phone but I had Hyperdrive 16 before I started this if that helps at all. I am stuck on samsung custom boot screen. I can get into odin recovery and tried recovery but keeps failing. can I get some help I need my phone i have to go to work soon. Thanks
ive tried the rootjunky video with both no wipe and full wipe neither worked. odin failed.
FlipFlop425 said:
ive tried the rootjunky video with both no wipe and full wipe neither worked. odin failed.
Click to expand...
Click to collapse
What files are you trying to flash? Did you use Safestrap to install RLS16?
Sent from my NCC-1701 using Tapatalk.
i had downloaded the new update for hyper drive. Right now my biggest probelm is I cannot get past the splash screen. I can get into download mode though so can we try to figure out how to unbrick me first. Download mode is the only thing I can seem to get into right now
FlipFlop425 said:
i had downloaded the new update for hyper drive. Right now my biggest probelm is I cannot get past the splash screen. I can get into download mode though so can we try to figure out how to unbrick me first. Download mode is the only thing I can seem to get into right now
Click to expand...
Click to collapse
That's why I need to know if you used Safestrap as your recovery. It's very likely you're trying to flash the wrong file with Odin.
If you had Safestrap your build wasn't MDK. If you didn't need Safestrap then your build was MDK.
So I'll ask again, what file are you trying to flash, with Odin, that keeps failing?
riker147 said:
That's why I need to know if you used Safestrap as your recovery. It's very likely you're trying to flash the wrong file with Odin.
If you had Safestrap your build wasn't MDK. If you didn't need Safestrap then your build was MDK.
So I'll ask again, what file are you trying to flash, with Odin, that keeps failing?
Click to expand...
Click to collapse
I used to have to use safestrap. I was trying to flash the mdk file from rootjunky's video on unbricking your phone
FlipFlop425 said:
I used to have to use safestrap. I was trying to flash the mdk file from rootjunky's video on unbricking your phone
Click to expand...
Click to collapse
NO!!! You cannot flash the MDK file, you cannot downgrade the S4! Always ends badly, go to the general section and grab the NC5 full-wipe tar and flash with ODIN.
npjohnson said:
NO!!! You cannot flash the MDK file, you cannot downgrade the S4! Always ends badly, go to the general section and grab the NC5 full-wipe tar and flash with ODIN.
Click to expand...
Click to collapse
I have tried that from SUrge1223. That did not work for me. I cannot get in to my phone to re root it. Is that the right file the one from him?
FlipFlop425 said:
I have tried that from SUrge1223. That did not work for me. I cannot get in to my phone to re root it. Is that the right file the one from him?
Click to expand...
Click to collapse
From here http://forum.xda-developers.com/showthread.php?t=2735172. I would choose the "Full Wipe" version. Make sure you have a good download. Check MD5. Make sure you follow the directions for Odin. If you verify all of that, and it still doesn't work, I'm afraid I won't be any more help. Someone with more knowledge than I have will have to step in. Good luck.
riker147 said:
From here http://forum.xda-developers.com/showthread.php?t=2735172. I would choose the "Full Wipe" version. Make sure you have a good download. Check MD5. Make sure you follow the directions for Odin. If you verify all of that, and it still doesn't work, I'm afraid I won't be any more help. Someone with more knowledge than I have will have to step in. Good luck.
Click to expand...
Click to collapse
I can vouch for the full Version. Saved my bacon.
You have to boot the phone into a special mode that will allow ODIN to funtion
Turn off the SGS4 and boot it into Download/Odin Mode: press and hold the Volume Down, Home and Power buttons simultaneously for a couple of seconds till you see a warning screen. Then press Volume Upkey to enter Download Mode.
I got it!!! Found my Samsung cable and all went well. TY for ALL the help!
FlipFlop425 said:
I got it!!! Found my Samsung cable and all went well. TY for ALL the help!
Click to expand...
Click to collapse
Yeah, it is a really good feeling when that ODIN starts to run like it means it. Nothing beats that first boot up!
I have a S4 i545 for Verizon. It was on 4.2.2 rooted and I upgraded using Fireflash with I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip. Everything seemed fine so I was using Titanium back up to remove the bloatware and then my battery died. When I charged it and booted up it got to the Verizon screen and hung there. I reset and tried several more times. I tried to use odin and flash a stock 4.2.2 ROM SCH-I545_VZW_1_20140330160240_yni63xq6zh and I also tried a 4.4.2 rom. Odin gave a an error and failed. I then tried going into the boot loader and flash the I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip also. Not sure if this was foolish or not but when I booted up I got to a black screen and there was a voice talking, maybe some sort of app that was running, but I couldn't do anything.
Right now when I turn on the phone it says firmware upgrade encountered an issue. Please select recovery mode in kies and try again. I tried connecting it to my computer and opening kies but it doesn't find it. If anyone can point me in the right direction on how to unbrick my S4 I would appreciate it. I know I screwed up.
as long as you can access ODIN you can unbrick. since your on 4.4.2 get the original rom and install. re root and install your rom of choice. from there if you have a previous backup in titanium you can restore
Sent from my LG-D415 using Tapatalk
I was on 4.2.2. I tried downloading the original ROM for this but it didn't work in Odin.
Problem is I can't get into download mode now, or recovery mode even. It's just at that screen I mentioned above. So Odin isn't recognizing my phone.
thats outside my knowledge base. sorry. good luck
Sent from my LG-D415 using Tapatalk
bump up
dr0832 said:
Problem is I can't get into download mode now, or recovery mode even. It's just at that screen I mentioned above. So Odin isn't recognizing my phone.
Click to expand...
Click to collapse
so if you hold down VOL- and power it doesn't go into download mode?
It won't be recognized in Odin until you get back to download mode. - in Odin then you'd want to flash the PIT file and the ROM you need.
The only other way to fix would be to get ahold of a copy of Verizon's Software Upgrade Assistant/Software Recovery Assistant, which looks like someone has uploaded here:
http://forum.xda-developers.com/showthread.php?t=2469615
The Software Recovery Assistant should fix it if nothing else does, I have used it before.
No when I turn it on it goes straight to the screen I mention with a yellow triangle and it does the same if I hold all the buttons down like you normally would to get in recovery.
I assume a battery pull didn't help. Since you have MDK, it MIGHT be worth it to get the JTAG dongle, which will boot the phone into download mode. It is about 3 bucks.
I tried installing in windows xp, windows 7 and windows 8 with no luck. I clicked the exe and it does nothing. I then tried installing on a MAC. It installed but when I went to run it the software opened for 1 second and then close with an error software closed unexpectedly. The I updated the software on the MAC and the software opened but the second I plugged in the phone it gave the same error. The MAC did find the phone though but windows did not.
bump
dr0832 said:
bump
Click to expand...
Click to collapse
Just plug the phone (on that screen) into your PC and see if it shows up in Odin.
If not, pull the battery, and hold the volume down and power buttons as you put the battery back in. Then choose Continue.
Did you read my post? I have done that. My phone is hard bricked. I can't get into recovery mode and therefore I can't get into download mode so therefore odin won't find my phone.
dr0832 said:
Did you read my post? I have done that. My phone is hard bricked. I can't get into recovery mode and therefore I can't get into download mode so therefore odin won't find my phone.
Click to expand...
Click to collapse
Which ROM did you flash, link?
Ahhh. The linked version of the Verizon Software Upgrade Assistant doesn't work. Sorry about that.
I just pulled the .iso from my S4 and posted it up, try this one: https://www.androidfilehost.com/?fid=24052804347780563
Per npjohnson advice I was able to get the phone into download mode. I misread your post at first so sorry about that. Now I need to figure out how to fix this. I flashed Lollipop originally so does that mean I can't actually go back to 4.2.2 using a stock ROM? Can someone point me to a ROM I should try to flash since the so called stock ROM's I have tried are failing in Odin.
I tried flashing this one:
http://stockroms.net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
It came from here:
http://galaxys4root.com/galaxy-s4-stock-firmware/
As for the Verizon assistant that was just posted it does not install just like the other. I click it and the screen flashed and then it does nothing.
dr0832 said:
Per npjohnson advice I was able to get the phone into download mode. I misread your post at first so sorry about that. Now I need to figure out how to fix this. I flashed Lollipop originally so does that mean I can't actually go back to 4.2.2 using a stock ROM? Can someone point me to a ROM I should try to flash since the so called stock ROM's I have tried are failing in Odin.
I tried flashing this one:
http://stockroms.net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
It came from here:
http://galaxys4root.com/galaxy-s4-stock-firmware/
As for the Verizon assistant that was just posted it does not install just like the other. I click it and the screen flashed and then it does nothing.
Click to expand...
Click to collapse
What lollipop did you flash originally? OTA?
I was rooted and then I flashed I545_OC1_Stock_DeOdexed_ROMwNK4_BL which I think is android 5.0.1. I used flashfire.
This was the thread I followed:
http://forum.xda-developers.com/gal...-to-update-to-i545oc1-5-0-1-keeproot-t3096558
Did the battery die on you? I think this is where you need the debrick image....
dr0832 said:
I was rooted and then I flashed I545_OC1_Stock_DeOdexed_ROMwNK4_BL which I think is android 5.0.1. I used flashfire.
This was the thread I followed:
http://forum.xda-developers.com/gal...-to-update-to-i545oc1-5-0-1-keeproot-t3096558
Click to expand...
Click to collapse
Probably should try the full factory image linked here: http://forum.xda-developers.com/gal...pment/odin-i545vrugoc1-factory-image-t3160125
That will put you on 5.0.1 OC1 including bootloader. You'll then root with Kingroot, use Super-sume to replace Kingroot with SuperSu and then you can use the NON-MDK ROM with FlashFire. (odex, or deodex if you want to use xposed modules.