I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
logannixon.la said:
I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
Click to expand...
Click to collapse
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
bigmike35 said:
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
Click to expand...
Click to collapse
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
logannixon.la said:
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
Click to expand...
Click to collapse
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
bigmike35 said:
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
Click to expand...
Click to collapse
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
logannixon.la said:
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
Click to expand...
Click to collapse
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
bigmike35 said:
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
Click to expand...
Click to collapse
So the stock Verizon firmware will repair the broken bootloader? I'll give it a go. Thanks for the info.
Just a quick update. I flashed the stock firmware for 4.4.2 and everything went over swimmingly. The phone now boots all the way into the Verizon boot splash screen. It then sits there and will not progress. I've tried wiping cache and factory resetting, but it still hangs on the Verizon splash screen. Any pointers?
Thanks again,
Nixon
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
logannixon.la said:
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
Click to expand...
Click to collapse
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
bigmike35 said:
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
Click to expand...
Click to collapse
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
logannixon.la said:
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
Click to expand...
Click to collapse
are you flashing it with the PIT file as well?
bigmike35 said:
are you flashing it with the PIT file as well?
Click to expand...
Click to collapse
I think I tried with and without, but I'll give it a shot.
logannixon.la said:
I think I tried with and without, but I'll give it a shot.
Click to expand...
Click to collapse
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
bigmike35 said:
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
Click to expand...
Click to collapse
I tried the pit to no avail. Currently wiping again just for fun. Not sure if it helps, but the system recovery screen reads this
Related
My Verizon Samsung Galaxy S4 (Model # SCH-I545) is stuck at an error screen with a yellow triangle in the middle and a picture of a phone on the left and a picture of a computer on the right. It also reads: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I JUST purchased this phone and the latest update was installed. I attempted to root the phone but after researching I found there is no current solution. I searched more and found a thread (that i can't post because I am a noob): I followed the instructions hoping to remove the update and return to stock, however the process did not work and Odin failed. Even though Odin was through, my phone still showed a line like it was downloading. I tried everything to reboot my phone, but could not find a way to do it, so I pulled the battery. Now, I cannot get past this screen. Is there anything I can do to fix this awesome blunder?
P.S. I am prepared for the scoldings I plan on getting...
I literally just posted the same question. Any help would be appreciated if you can figure it out. Ill return the favor if i can get any information :good:
If you took the latest update I'm not sure what the answer is because I haven't been willing to take the update.
If you were in mdk before the yellow triangle then all you have to do is Odin the mdk kernel.
I'd imagine if you are on the latest then odining the latest would take care of it also but again, I won't take the latest so I can't say for sure
sent from my blu vzw gs4
Thanks Jakemkv, I will update you as I get more info. I will also be looking at your thread, you can bet.
Dubbsy, where can I find that new mdk Kernel?
richardawood said:
Thanks Jakemkv, I will update you as I get more info. I will also be looking at your thread, you can bet.
Dubbsy, where can I find that new mdk Kernel?
Click to expand...
Click to collapse
Im on a search for the updated kernel as well. At least there is someone in the same boat as i am.
richardawood said:
My Verizon Samsung Galaxy S4 (Model # SCH-I545) is stuck at an error screen with a yellow triangle in the middle and a picture of a phone on the left and a picture of a computer on the right. It also reads: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I JUST purchased this phone and the latest update was installed. I attempted to root the phone but after researching I found there is no current solution. I searched more and found a thread (that i can't post because I am a noob): I followed the instructions hoping to remove the update and return to stock, however the process did not work and Odin failed. Even though Odin was through, my phone still showed a line like it was downloading. I tried everything to reboot my phone, but could not find a way to do it, so I pulled the battery. Now, I cannot get past this screen. Is there anything I can do to fix this awesome blunder?
P.S. I am prepared for the scoldings I plan on getting...
Click to expand...
Click to collapse
If the phone was running ME7 then you can ONLY flash ME7 again (at least right now).
Grab the image from this thread...
http://forum.xda-developers.com/showthread.php?t=2357235
and flash it using Odin.
Thank You
That worked great! I am back up in running and waiting patiently w/ the rest of us that updated... THANK YOU!!!!!! :highfive:
Thanks
I can't thank you enough. The S4 is my first Android phone and after 3 weeks, the USB connection on the phone broke and I finally got my new one today. While I was setting up SuperSU/Titanium Backup/ROM Manager, I guess the phone downloaded the ME7 update in the background and I told it to install (stupid me). This will teach me from rushing to get my phone back to the state it was in. (Not that I can do that now because I need SuperSU before I can install ROM Manager). Hopefully once I can get ROM Manager back, I can restore my MDK backup with all my custom settings and apps. I think I will make a visit to the VZ store tomorrow and see if they can revert back to the MDK version. I will make up some lame excuse of why I don't want to be on this new release.
This leads to my question of, is there a way to disable or remove the apk file that controls the software updates?
Thanks again for saving my life!!!
Once you take me7 update theres no going back unless you get a different phone. When someone gets the me7 ota rooted you can rename/remove sdm.apk and itll keep your phone from downloading new updates. I would say freeze as well but some users reported their phones updating even with it froze. When the me7 bootloader/recovery situation gets resolved there wont be much reason to go back to mdk anyway since people will start creating roms with it as the base.
SCH-I545 using Tapatalk 2
Thanks
hexitnow said:
Once you take me7 update theres no going back unless you get a different phone. When someone gets the me7 ota rooted you can rename/remove sdm.apk and itll keep your phone from downloading new updates. I would say freeze as well but some users reported their phones updating even with it froze. When the me7 bootloader/recovery situation gets resolved there wont be much reason to go back to mdk anyway since people will start creating roms with it as the base.
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the information about the sdm.apk. When I debloated my phone I used the adb shell to remove most of the *.apk packages that I did not want. This was of course after I took a full Titanium Backup and ROM Backup.
Sounds good and I will not waste my time going to Verizon today.
You make a really good point about not going back to the mdk, but rather move forward with the technology and updates. This leads me to some more questions once I have root again:
1. Is my mdk rom backup totally useless at this point?
2. If yes to 1, since my mdk rom contained all my apps/customized settings, do I have to manually download everything and reconfigure?
3. If no to 2, how would I go about getting the app/customized settings back, Titanium Backup?
4. If yes to 2, if I go about downloading everything manually and configuring, will the new root remove all these settings?
I am sure I will have more questions so thanks in advanced
PS: I think I figured out what caused my USB port to stop working. I take my phone with me when I run so I think some sweat got in from my arm band and corroded the connections. I tried cleaning them with rubbing alcohol and compressed air, but still no dice. If connected to a computer or wall charger, it will charge, but a computer will not detected it. So my guess is there is damage to the board allowing whatever communication is needed to work with a computer.
Hi,
I need help guys.
I have S4 and I was trying to mess with it and now I don't have it at all. (pic 1)
the Samsung logo and unlock lock icon are as far as my phone goes now, and after that u cant even power it off u have get battery out. (pic 2)
I am able to go to download mode (pic 3)
and I was able to get to there (up+menu+power key), but now I cant even go there. I get black screen when I am trying to do it. (pic 4)
Thanks for your time,
Ps. Help me
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
answer
Eeiden said:
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
Click to expand...
Click to collapse
I was trying to flash rom, I was trying to make in international phone so it could work in Europe with out any Verizon build in stuff, just pure Samsung.
I can go do download mode, I was able to go for recovery before. That why there is the 4th picture, in stead of regular recovery a had that "teamwin" screen. Now when I press up menu and power is saying its going to recovery boot but then it resets it self and going back to Samsung unlock icon screen and just stays there...
You hold volume down + power to get to download mode. Then connect to a pc and download the all in one tool found in the development thread. Ignore the messages about having your phone in USB debugging and tell it to flash twrp 2.6.0.0. If it doesn't take In download mode, try rebooting your phone while it tries to flash twrp.
If that doesn't work flash stock with Odin and re-root and unlock the phone.
Sent from my SCH-I545 using xda app-developers app
I'm having the exact same problems right now. I tried flashing a 4.3 i9505 rom and now I can't get back into recovery and I can't boot into the OS. I can get into download mode and use ODIN, but I don't know what to do from there. I tried using the All-In-One tool to install TWRP, but it just says Device Not Found. I also tried flashing the stock sch-i545 kernel in ODIN, and it completed successfully, rebooted, and its still doing the same thing. Is there some other way that I've missed to return to stock? I'm kinda bummin here.. but thats what comes with the territory I suppose. Any help you can offer would be greatly appreciated. Thanks.
Found the factory image thread. Going to follow instructions. Will report back.
it works but not completly
So guys going back to my problem I was trying to do everything like lahma69 was trying too...
in odin was error that device not found, all off that...
but what I did, I look more online and I found this one guy...
and what I did in download mode I use odin, and in PDA selection I use this file stockroms(dot)net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
now boom... its kinda works... I am back with my os, I got the android root.
but some things are not right... my phone is very hot, maybe because its charging its self for the first time in weeks.
more important is Whats is happening right now, in boot menu I get errors, no commands, it was not able to do factory reset until I went into os and did it over there... and I cant do software update from Verizon... it goes to root and its trying but then gets error and going back to os...
and I am worry about that file that I download...
so we got little progress and lahma69 I can at least operate os and I have back stock root...
but until we will not going to make it 100% hold on with what I did...
U cant flash a rom thats not made specifically for the verizon variant (i545). The i9505 is the international version of the phone. Hence your phone not booting. Youre going to have to flash the stock mdk firmware through odin and start over (reroot, etc).
SCH-I545 using Tapatalk 2
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
lahma69 said:
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
Click to expand...
Click to collapse
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
SaNNeK said:
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
Click to expand...
Click to collapse
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
root problem and upgrate
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
SaNNeK said:
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
Click to expand...
Click to collapse
Did you see what I said about doing Samsung software updates? The rooting threads for the Verizon GS4 say that the new VRUAME7 OTA update can't be rooted. After flashing the stock image from oden, why don't you reroot your device according to http://forum.xda-developers.com/showthread.php?t=2290798 and then install Goomanager, click the menu key, click "Install open recovery script" and that will install TWRP recovery. From there, flash a verizon rom of your choice and all should be well, no? I only use TWRP so I can't give you any input on other recoveries. Make sure you didn't somehow get updated to VRUAME7.
township japinove
lahma69 said:
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
Click to expand...
Click to collapse
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
SaNNeK said:
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
Click to expand...
Click to collapse
Whats your build number in Settings -> About Phone ?
lahma69 said:
whats your build number in settings -> about phone ?
Click to expand...
Click to collapse
jdq39.i545vruamdk
Working progress
SaNNeK said:
jdq39.i545vruamdk
Click to expand...
Click to collapse
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
SaNNeK said:
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
Click to expand...
Click to collapse
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
lahma69 said:
And by the way,for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
And thats the most important part, because if you do you will lose root and your ability to customize your phone. In layman's terms? You will be re-VZ-navigated.
I am having a similar issue. Got the "Samsung Custom" boot screen with no boot to the OS after clean wipe and install of Hyperdrive 7. Since then I have been troubleshooting the issue and have tried many things including the "No-Wipe Factory Image". Once complete I am still getting the Samsung Custom boot screen and no loading of the OS.
Any ideas as to what I can try.
Thanks in advance,
Tony
lahma69 said:
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
as my understanding its not.. I just did that no wipe recovery...
sorry I was out of town today... so I assume I will have to do root but which one is the best? there is so many different ones...
Hey all. I had Hypderdrive installed. I updated it to 21 but had a force close issue. I wiped to reinstall in safestrap and realized that I didn't have the ROM on the device anymore. Whoops. All of a sudden I had no OS and couldn't connect to the phone via USB to put the ROM onto it.
After trying some stuff I got a bit more stuck. I can only reboot into 3 places: 1) Download mode (with volume down) 2) stuck at samsung unlocked icon (no buttons pressed) and 3) default recovery mode (with volume up). I tried with Kies to just install the latest firmware, figuring I'd be happy with lollipop and just go ahead and get a new phone in the near future. That firmware upgrade process fails right when the status bar shows up on the screen. Now rebooting the phone says Software Update Failed.
What are my options via Kies, Odin, or something else to either get back to rooted Hyperdrive or just get the latest firmware up and running? Thanks!
ODIN v3.10
https://docs.google.com/file/d/0B4RU_ZH5QUASNmxLX3JpejBXREE/edit?usp=docslist_api
This is the SCH-I545 lollipop image:
https://docs.google.com/file/d/0B4RU_ZH5QUASaU9LcDJ3WWZfdXM/edit?usp=docslist_api
And once you go forward..There is NO ROOT or ROMMING!!!
If you want to stay NK1 and ROOT:
https://docs.google.com/file/d/0B4RU_ZH5QUASdHE1b2Q2NXpVX0U/edit?usp=docslist_api
In ODIN, WITH EITHER file select these checkboxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Phone EFS CLEAR
Thanks a ton. Haven't gotten it to work yet. I followed your directions and Odin fails with "SW REV. CHECK FAIL : fused : 7, Binary : 6". My guess is that is a mismatch of the bootloader versions? I believe I was on NC5 before, so I tried flashing the No Wipe file from here: http://forum.xda-developers.com/showthread.php?t=2735172 and had no luck.
Any idea what version I should be trying to get it to work? Thanks for the help so far!
No. That means you are on lollipop Bootloader already! You have to flash lollipop
KaosMaster said:
No. That means you are on lollipop Bootloader already! You have to flash lollipop
Click to expand...
Click to collapse
Yup. Learned that while I was thinking about it. Such is life, right? Currently trying to just get OC1 installed via Odin but it keeps failing late in the process with XmitData_Write. If anyone has an idea beyond changing cables and ports (which I'm doing now) then I'm all ears.
Quick update. I've been following the instructions and advice from this thread: http://forum.xda-developers.com/galaxy-s4-verizon/help/unbrick-taking-oc1-t3122230
I have not yet gotten my phone working, but have made slight progress. I'm currently flashing from the Software Update Failed screen and not the Odin Download Mode screen. I've been checking all the listed boxes. I've tried flashing as CSC and as AP and it is now failing on the NON-HLOS.bin file. It's failed there 4 or 5 times now.
Any advice on what changes to try next?
volantis said:
Quick update. I've been following the instructions and advice from this thread: http://forum.xda-developers.com/galaxy-s4-verizon/help/unbrick-taking-oc1-t3122230
I have not yet gotten my phone working, but have made slight progress. I'm currently flashing from the Software Update Failed screen and not the Odin Download Mode screen. I've been checking all the listed boxes. I've tried flashing as CSC and as AP and it is now failing on the NON-HLOS.bin file. It's failed there 4 or 5 times now.
Any advice on what changes to try next?
Click to expand...
Click to collapse
the Single Service File goes in the CSC box. Not sure why it keeps failing, but my OPinion is that you should Try to Load into Recovery, Perform A Factory Data Reset then Try again!
Flash with the Check-Boxes befoire without the "Phone EFS Clear" option...When THe phone turns on....if it is The firmware Recovery screen...Flash there, if it is the Samsung LOGO, Pull the Battery, and LOAD into "Odin Mode" and Flash AGAIN There!
KaosMaster said:
the Single Service File goes in the CSC box. Not sure why it keeps failing, but my OPinion is that you should Try to Load into Recovery, Perform A Factory Data Reset then Try again!
Flash with the Check-Boxes befoire without the "Phone EFS Clear" option...When THe phone turns on....if it is The firmware Recovery screen...Flash there, if it is the Samsung LOGO, Pull the Battery, and LOAD into "Odin Mode" and Flash AGAIN There!
Click to expand...
Click to collapse
Thanks. I finally got it working. I'm not sure exactly what did it. I kept trying various combinations of flashing at CSC or AP and in Download mode and Software Upgrade Failed. I believe the one that actually took was the Sammobile stock OC1 file flashed as AP, but I'm not 100% and not sure that really is what made the difference. I did have all the options checked when it finally took.
After the Odin flash passed it did just boot to a black screen with the LED on solid blue. I went to recovery and did a factory reset and the phone booted up. Maybe that'll help someone else.
Don't have root anymore, but Lollipop seems like a very nice update coming from KK.
Thanks! - but still in trouble.
Spoke too soon!! Yours was the only one that actually loaded with Odin. After that phone will not reboot, just comes on for 2 seconds and then turns off. Any ideas would be greatly appreciated.
I have tried the following firmware versions, except for yours, they all get fused: 7 , binary : 6:
I545_VZW_I545VRUDMI1_I545VZWDMI1_Original
I545_VZW_I545VRUEMJ7_I545VZWEMJ7_Original
VZW-I545VRUFNC5-20140429111807
VZW-I545VRUFNG6-20141021092718
plus several others
--------------
Thanks, bricked my Verizon S4 and tried 5 different firmware files, including the ones from the Samsung site. Yours is the only one that worked.
Looks like you need to flash a more recent file. You'll probably have to go with the latest stock version without root.
volantis said:
Looks like you need to flash a more recent file. You'll probably have to go with the latest stock version without root.
Click to expand...
Click to collapse
Sorry, thought I updated the post. I tried again and the second time around it worked all the way through with the file on this thread.
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Anyone? Even a, "Yeah, that's weird man! Sounds like you did everything right!" Would make me feel better...
Yes I've tried it and it worked make sure u have the unofficial safestrap the one for your phone and do the busy box and terminal emulator thing and it works if you try to install safestrap without the other things you will brick I did it twice but it very easy to unbrick so download busybox terminal emulator and the correct safestrap for you device and also I'm on 4.4.2 also and there is only one rom i have found that works and its called superliter there ya go hope I help would provide download links but I'm not home
Also I forgot to mention your bootloader won't be unlocked it'll be bypassed and you will have a custom recovery
androidforums.com/threads/verizon-verizon-bootloader-unlock.856221/page-2[/url]
forum.xda-developers.com/showthread.php?t=2605648
device specific safestrap recovery and image
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
schmitey said:
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Click to expand...
Click to collapse
Verizon spends a pretty penny when it comes to making sure their devices................. stay theirs i guess you can say when it comes to the boot-loader! To my knowledge their isn't a way of getting around that with a permanent recovery flash that completely replaces Verizon's stock recovery. I can almost guaranteeing you that your problem is Verizon locked boot loader. Stock recoveries are solely only their for their technicians, so unless someone somehow has leaked a program that they use to get around that stuff without screwing it up, we the general public will never be able to flash anything permanent with any phones stock recovery unless we have their "secret" software! Every once in a while you do find a leaked one. I got lucky and found one for the T-mobile galaxy S6 Edge. As far as Odin I've noticed that the new versions seem to be very particular. Meaning if a dot or a space is misplaced anywhere in the zip or what not it will always fail. With my t-mobile S6 I spent two days figuring out I had to take a letter out of the name of the file i was trying to Odin. One letter that was it and once I did that it went flawlessly. Otherwise man i really don't know what to tell you, seems like ya followed the lines as described. Just remember its a Samsung Galaxy in my opinion Galaxies are unbrickable. Ive even pulled the cord in the middle of a Odin flash to see if i could brick it for good and was still able to go right into download mode and flash stock back onto it and everything working. So don't be afraid of bricking it. It will be way easier (sorry to say) for you to re-flash stock right now! Good luck bro wish you the best!
---------- Post added at 08:25 PM ---------- Previous post was at 08:18 PM ----------
schmitey said:
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
Click to expand...
Click to collapse
Are you able to disable Signature verification in the recovery?
Are you able to disable Signature verification in the recovery?
You can once I flash to say clockworkmod recovery. Stock I don't know of a way to...hence the Catch 22 there's no going forward and no going back...you're stuck with stock ROM/recovery but at least its rooted.
Well ****. Take my word for it you CAN brick a galaxy s3.
I used KIES to restore back to factory stock recovery etc etc.
I then used towelroot to root phone and install supersu. I then installed safestrap which totally worked! I was able to bypass the stock recovery and everything was running smoothly...I got overzealous and tried to install the cyanogenmod vrale6 bootloader zip through safestrap. I currently have a brick. It won't boot, no led's, no screen, no vibrate. I have another galaxy s3 charging batteries and swapped it out...removed sim and micro sd. I should have just installed the cyanogenmod app and done it that way...
So close and now I bricked it...
OK got my brick back by writing image to microSD card...pretty happy about that little trick. And that's utter nonsense about needing the same size card as your internal memory! I used a 32gig card on a 16gig phone...
Still trying but this locked 4.4.2 bootloader is BULL****. Going to try to downgrade but I'm not sure I'm going to end up with anything but a rooted stock rom...
So does anyone know of a way to downgrade or change recovery on Verizon 4.4.2?
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
slimcyril said:
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
Click to expand...
Click to collapse
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
schmitey said:
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
Click to expand...
Click to collapse
Well no zip has ever failed on my end using safestrap, does your device have init.d support?
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
schmitey said:
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
Click to expand...
Click to collapse
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
slimcyril said:
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
Click to expand...
Click to collapse
system partition is NOT checked within safestrap. Installed universal init.d but I'm out of my league on it... Init.d says stock kernel does not have support...
I have internetted to the best of my ability and tried many, many different things, but I cannot get my Note 2 to root. Odin keeps failing on NAND or on restore.img or any other step. I have tried every usb port and every cable in my house. I tried this once before (maybe a year or two ago) and managed to get a verizon "unauthroized software" message. From this, I was able to get it back to stock, and I have left it alone since.
Now this is no longer my main phone, and I WILL root it, but I need some help.
It is deactivated (my service phone is now an old Fascinate).
It is SCH-I605, on 4.4.2, baseband is I605VRUFND7, kernel is 3.0.31, build is KOT49H.I605VRUFND7.
The phone is in developer mode, USB debugging is enabled, verify apps is disabled, and I don't have an option to "unlock OEM". I (currently) have Odin 3.10 and 3.12 on my desktop. I've got a thing called "CF-Auto-Root-t0ltevzw-t0ltevzw-schi605" which I believe it some kind of "patch" for the kernel that will grant root access.
I can boot the phone to recovery/download mode. I can start Odin, I can connect the phone, I can see it in Odin (usually on COM5). In NONE of the versions of Odin I have seen, do I ever see this "PDA" button, but I do have a AP button. Depending on the version of Odin, usually AP is the only button that is enabled. One of the tutorials talks about PDA button but the screenshot shows the AP button, so I have been trying this exclusively.
I can click start, and things will work pretty good for a little while, but then I will get some error. Usually it is on recovery.img, sometimes it is on NAND rewrite (I think ... I can't get back there). Always just "FAIL!". I cannot find a log to tell me why, and the message is completely useless. Sometimes it will just hang on SetupConnection, and once it hung on recovery.img for over 10 minutes.
The last time I did this (and recovered) I was on Win 7, now I'm on Win 10.
Can somebody please offer some advice? I can provide screenshots, chat on Skype, whatever is needed. Thanks!!
Emery
I also want to mention that I tried ghetto root but I am getting errors in it as well. The main error is that there is an unexpected newline (but I do not know which file), and then I am told that root fails, and Super SU does not appear on the phone.
i used Saferoot and it seems to work each time...
Forum
http://forum.xda-developers.com/showthread.php?t=2565758
SafeRoot Link:
http://forum.xda-developers.com/attachment.php?attachmentid=2760984&d=1400951117
Jaws4God said:
i used Saferoot and it seems to work each time...
Forum
http://forum.xda-developers.com/showthread.php?t=2565758
SafeRoot Link:
http://forum.xda-developers.com/attachment.php?attachmentid=2760984&d=1400951117
Click to expand...
Click to collapse
Thanks! I will try it right now!
Ok. So saferoot failed with "Your kernel is patched! This device is not supported."
I think it also said something about a locked bootloader, so I went looking for more information and found
http://forum.xda-developers.com/showthread.php?t=2118348
I tried "no you verizon" version first, which said that it failed (I took a copy of the log).
Then I tried the earlier "Back Atcha Verizon", and now I am back to "system software not authorized by verizon ..... blah blah go to the nearest verizon store for help".
Lol, now I have to remember how to undo this ... I think I had to restore the stock image with Odin or something.
In any case, what the heck is possibly going on? How is this the most locked-down phone on the planet? This is incredible and ridiculous and I don't even know!
emeryalan said:
Ok. So saferoot failed with "Your kernel is patched! This device is not supported."
I think it also said something about a locked bootloader, so I went looking for more information and found
http://forum.xda-developers.com/showthread.php?t=2118348
I tried "no you verizon" version first, which said that it failed (I took a copy of the log).
Then I tried the earlier "Back Atcha Verizon", and now I am back to "system software not authorized by verizon ..... blah blah go to the nearest verizon store for help".
Lol, now I have to remember how to undo this ... I think I had to restore the stock image with Odin or something.
In any case, what the heck is possibly going on? How is this the most locked-down phone on the planet? This is incredible and ridiculous and I don't even know!
Click to expand...
Click to collapse
weird.. yeah i used saferoot on my device a few times and haven't had an issue.. it shouldn't matter if your bootloader is locked.. that would only keep you from flashing a customer recovery...
I know mine is running 4.1.2 (MC3) so I should be able to unlock my bootloader but can't got get CASUAL to work... just fails at different points or loops trying to install CAD or something... so not sure what i need to do.
I did try to use Flashify to put a custom recovery on.. i got the "system software not authorized... " blah blah.. knew I did have to use ODIN to restore the factory firmware.. but it wasn't reading my phone.. finally after switching USB ports, it worked and I was able to put it back to stock and get it to boot and root again..
so if anyone has any ideas on how to get CASUAL to work, please let me know.
Galaxy Note 2 lessons from Verizon
There is still no root or bootloader unlock for Verizon Galaxy Note2 (Model SCH-I605). Ours quit working, by shutting down/locking up often. From what I've found out, this behavior is caused by Verizon's own software, not the hardware, forcing us to get a new phone. I STRONGLY recommend anyone on Verizon to drop the service immediately, before this becomes the standard. What we will see is, having to purchase a new phone product every two years, requiring us to turn in the old phone, then being sold a repackaged refurbished model at new phone prices.
Verizon is pushing the boundaries, and they are preventing a piece of equipment that you own from functioning in order to force you to buy another of their products. If allowed, this business model WILL spread to all their competitors. It will stunt the growth of future technologies since innovation will not be the motivation to buy a new product, the only motivation being the continual failure of a sabatoged product.
So again, please drop Verizon if you have them, and if you don't have them don't get them.
update.. i was able to get CASUAL to work.. had to download another program to reset the CAD Driver.. then it worked like a charm.. so have an unlocked bootloader and rooted. Right now i'm trying out Alliance ROM..
emeryalan said:
Ok. So saferoot failed with "Your kernel is patched! This device is not supported."
Click to expand...
Click to collapse
yep, i got this error too after I had tried Alliance 4.4 ROM... so I guess that saferoot only works for 4.3 and older..
LordBaronMarshall said:
There is still no root or bootloader unlock for Verizon Galaxy Note2 (Model SCH-I605). Ours quit working, by shutting down/locking up often. From what I've found out, this behavior is caused by Verizon's own software, not the hardware, forcing us to get a new phone. I STRONGLY recommend anyone on Verizon to drop the service immediately, before this becomes the standard. What we will see is, having to purchase a new phone product every two years, requiring us to turn in the old phone, then being sold a repackaged refurbished model at new phone prices.
Verizon is pushing the boundaries, and they are preventing a piece of equipment that you own from functioning in order to force you to buy another of their products. If allowed, this business model WILL spread to all their competitors. It will stunt the growth of future technologies since innovation will not be the motivation to buy a new product, the only motivation being the continual failure of a sabatoged product.
So again, please drop Verizon if you have them, and if you don't have them don't get them.
Click to expand...
Click to collapse
Even though my device is bootloader unlocked for testing CM releases I always go back to stock ND7 for stability minus bootloader then Ghettoroot and it's been working solid for years. And, unlimited data for $60 is hard to beat. Absolutely nothing wrong with the phone and software and not yet with the service as long as I can avoid the $20 unlimited data increase when contract expires in 2017.
mi7chy said:
I always go back to stock ND7 for stability minus bootloader then Ghettoroot and it's been working solid for years. .
Click to expand...
Click to collapse
what version is ND7 ? thank you.
Jaws4God said:
what version is ND7 ? thank you.
Click to expand...
Click to collapse
ND7 is Kit Kat 4.4.2.
mi7chy said:
ND7 is Kit Kat 4.4.2.
Click to expand...
Click to collapse
oh got ya. i haven't read much about that version.. wonder if it has possibility of unlocked bootloader or root.
Jaws4God said:
oh got ya. i haven't read much about that version.. wonder if it has possibility of unlocked bootloader or root.
Click to expand...
Click to collapse
It's the last official release. If you're already bootloader unlocked you can use Mobile Odin Pro to flash it minus the bootloader then use Ghettoroot. Only thing is Mobile Odin Pro only works with Lollipop such as CM12.1 or older. So, if you try CM13 and decide to go back to stock ND7 you have to first flash CM12.1 then use Mobile Odin Pro to flash stock ND7.
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
mi7chy said:
It's the last official release. If you're already bootloader unlocked you can use Mobile Odin Pro to flash it minus the bootloader then use Ghettoroot. Only thing is Mobile Odin Pro only works with Lollipop such as CM12.1 or older. So, if you try CM13 and decide to go back to stock ND7 you have to first flash CM12.1 then use Mobile Odin Pro to flash stock ND7.
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
Click to expand...
Click to collapse
oh interesting.. so right now i'm on a ND7 port.. should I bother flashing the ND7 without bootloader or is not really needed?
Thanks!