Where can I get a quick download of the stock MK2 besides SamMobile? I can't find it anywhere besides there and it takes like two hours or more to download. Would be great if I could get this without a data wipe too. Thanks
http://forum.xda-developers.com/showthread.php?t=2578209
There ya go, just pop it into odin and flash.
ppat324wi said:
http://forum.xda-developers.com/showthread.php?t=2578209
There ya go, just pop it into odin and flash.
Click to expand...
Click to collapse
Thanks a ton!! :good:
ppat324wi said:
http://forum.xda-developers.com/showthread.php?t=2578209
There ya go, just pop it into odin and flash.
Click to expand...
Click to collapse
Another quick question...I'm running stock rooted MK2 and want to trade my phone back to VZN to "edge up" to another phone. I currently have the custom icon on startup so will running the full wipe stock tar get rid of this? I have already flashed the no wipe and still have it
rleague81 said:
Another quick question...I'm running stock rooted MK2 and want to trade my phone back to VZN to "edge up" to another phone. I currently have the custom icon on startup so will running the full wipe stock tar get rid of this? I have already flashed the no wipe and still have it
Click to expand...
Click to collapse
Flashing the full wipe tar should remove the custom icon. The initial boot up screen after successfully flashing the full wipe tar will have the custom icon but dont worry, after the phone boots up, reboot it and it should be gone.
Sent from my SCH-I545 using XDA Free mobile app
Related
Hey guys, I need help.
I consider myself fairly adept at handling rooted devices, but I have not been following development for the GS4 for the last several months and have been running the last release of Synergy before their hiatus.
I was going to try out something different. I always enjoyed Beanstown's Jelly 'Beans', and thought I would try Build 7.
Now I am stuck at the Samsug Galaxy Boot Logo and it never goes to the Custom Boot Screen.
WORSE...I managed to break my recovery...so it will not boot their either.
Only mode I can boot to is Download.
Maybe I am just blind but I searched and could not find any Odin flashable recoveries...does anyone have one? Is there a rooted MDK file out there that I can flash via Odin?
Someone please help
Did you do the proper wipes when flashing the new rom? There arent any odin flashable recoveries for the s4. I would probably use the no wipe mdk image to recover (wont lose any user data) since you have no custom recovery to flash something with. Youll have to start over but youll have a working phone at least.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
jbg25 said:
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
Click to expand...
Click to collapse
Yeah looks like you got everything in order. Rom manager or rom toolbox will auto loki the recoveries. No need to update radios when flashing beans either. Itll already have the radios included unless your wanting to flash the mj7 radio seperately then I believe youll be ok doing that. I havent done alot of reading on the newest radios.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
jbg25 said:
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
Click to expand...
Click to collapse
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
beanstown106 said:
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
Click to expand...
Click to collapse
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
jbg25 said:
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
Click to expand...
Click to collapse
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
jbg25 said:
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
Click to expand...
Click to collapse
Go here. Get 2.5.0.2
http://techerrata.com/browse/twrp2/jfltevzw
Instructions
http://teamw.in/project/twrp2/181
At the bottom of the page.
Edit;
Or flash this in recovery
http://forum.xda-developers.com/showthread.php?p=45006486
I would reboot to recovery after flashing to make you got it on the right version.
Then make sure you can still boot back to your rom.
Then go back to recovery
Wipe
Factory reset.
Advanced
Check system, Data, davlik and cache
Wipe
Go back to main screen
Install
Fund your rom to flash.
Sent from my SCH-I545 using xda app-developers app
Me too. I tried the [ROM][TW4.3]STOCK-ROOTED-MJ7-AROMA-LOKI'd ROM with CWMR. Wiped Dalvik. Cache, Ractory Rest/Data. Seemed to install fine but then hung at "Custom". Fortunately I was able to a Nandroid Restore but not sure where this went wrong. Finally got TWRP to install after several failed GooManager attempts over the past month. May CWMR is the problem.
I soft bricked my phone. I can get back to TWRP, and any ROM seems to take but none will boot. All stuck on the Samsung Custom (open lock) screen.
I think i formatted too much and now need to go back to MDK.
Any suggestions for the speediest solution?
My thoughts are odin MDK and then root and flash TWRP?
orateam said:
I soft bricked my phone. I can get back to TWRP, and any ROM seems to take but none will boot. All stuck on the Samsung Custom (open lock) screen.
I think i formatted too much and now need to go back to MDK.
Any suggestions for the speediest solution?
My thoughts are odin MDK and then root and flash TWRP?
Click to expand...
Click to collapse
Odin is probably only choice
powered by hashcode safestrap hyperdrive 10.2
decaturbob said:
Odin is probably only choice
powered by hashcode safestrap hyperdrive 10.2
Click to expand...
Click to collapse
I did it. Luckily i was able to odin back to an MDK ROM, re-root and recovery. All is well. I always thought you couldn't go back to MDK, but i guess you could. Does that mean anyone on a ROM today can go back to MDK?
orateam said:
I did it. Luckily i was able to odin back to an MDK ROM, re-root and recovery. All is well. I always thought you couldn't go back to MDK, but i guess you could. Does that mean anyone on a ROM today can go back to MDK?
Click to expand...
Click to collapse
The reason you could go back to MDK, because you were on MDK build. People won't be able to odin back to MDK after they take OTA update.
urcboss07 said:
The reason you could go back to MDK, because you were on MDK build. People won't be able to odin back to MDK after they take OTA update.
Click to expand...
Click to collapse
i wasn't on the MDK build. I had already moved to a custom rom of ME7 and was on hyperdrive 4.3 when i did the ODIN. Is it because i wasn't bootlocked?
orateam said:
i wasn't on the MDK build. I had already moved to a custom rom of ME7 and was on hyperdrive 4.3 when i did the ODIN. Is it because i wasn't bootlocked?
Click to expand...
Click to collapse
Flashing a custom ROM doesn't change your original baseband. If you didn't take any official OTA's then you were still on MDK. Also, there's no such thing as an unlocked bootloader for the S4's.
Sent from my NCC 1701 Using Tapatalk 4
riker147 said:
Flashing a custom ROM doesn't change your original baseband. If you didn't take any official OTA's then you were still on MDK. Also, there's no such thing as an unlocked bootloader for the S4's.
Sent from my NCC 1701 Using Tapatalk 4
Click to expand...
Click to collapse
Your right. I just checked my baseband on my current ROM (recently released hyperdrive r11) and it's MDK.
So does the baseband have any affect on my usage?
ugh i installed this and i cant get past the Samsung logo either... which file should i download to odin??? not what i wanted to deal w/ right before bed.. hopefully the process doesn't take too long.
Powell730 said:
ugh i installed this and i cant get past the Samsung logo either... which file should i download to odin??? not what i wanted to deal w/ right before bed.. hopefully the process doesn't take too long.
Click to expand...
Click to collapse
Boot into the factory recovery and do a wipe/factory restore.
didnt realize this was possible if we're on a custom recovery. i thought factory recovery was erased once you install a custom one?
Powell730 said:
didnt realize this was possible if we're on a custom recovery. i thought factory recovery was erased once you install a custom one?
Click to expand...
Click to collapse
You will wipe the custom recovery when you odin. After that just boot into recovery and select wipe/factory reset.
I've had this problem since December or so now, (whenever CM11 came out) and I've tried asking for help everywhere, including here before. But I'm sending out one final hail mary request. For some reason, whenever I download a 4.4 Rom for my phone and I have my wifi running, the phone will freeze after I hit the power button and will not turn the screen back on at all or it will freeze while I'm using it. The only way to get the phone back on is by doing a battery pull.
Here is everything I've tried: various Roms, various kernels, different steps to install (full wipe, wipe cache, etc.), I've even unrooted and gone back to stock to start from scratch and it still happens.
If anyone could please help me out, I'm stuck running 4.3 and I want to be able to run 4.4. Hopefully I can finally find a fix for this issue I'm having. I don't think it's faulty hardware because one other person or so has had the problem as well. Help me XDA, you're my only hope!
What firmware do you have? Since you mentioned different kernels, are you still on MDK? Have you ever taken any if the OTA updates?
Sent from my SCH-I545 using Tapatalk
jmgib said:
What firmware do you have? Since you mentioned different kernels, are you still on MDK? Have you ever taken any if the OTA updates?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah I'm still on MDK. And no I never did an OTA.
What recovery are you using?
It happens to you all the time now? I've been so busy with work and school now that I hardly have any time at all. I really do want to pinpoint the issue before I throw this thing out the window....lol
thesoldier said:
It happens to you all the time now? I've been so busy with work and school now that I hardly have any time at all. I really do want to pinpoint the issue before I throw this thing out the window....lol
Click to expand...
Click to collapse
Me too ha, like I said this is my final hail mary. If I can't get it fixed I'm going to buy a new phone and I really don't want to have to do that. I'm praying one final time for someone to figure a fix for me.
joshm.1219 said:
What recovery are you using?
Click to expand...
Click to collapse
I've used CWM and TWRP. Currently using TWRP.
Nwwolf1 said:
I've used CWM and TWRP. Currently using TWRP.
Click to expand...
Click to collapse
This what I would do if I was you.
Flash full wipe MDK tar file
Root using towelroot
Install latest TWRP via flashify
Flash jrkruse's stock 4.4.2 NC5 rom for MDK, picking the stock talexop kernel in aroma.
If that doesn't work, I don't know what to tell you.
joshm.1219 said:
This what I would do if I was you.
Flash full wipe MDK tar file
Root using towelroot
Install latest TWRP via flashify
Flash jrkruse's stock 4.4.2 NC5 rom for MDK, picking the stock talexop kernel in aroma.
If that doesn't work, I don't know what to tell you.
Click to expand...
Click to collapse
Will I be able to still run AOSP Roms or will I have to stick with TW?
Nwwolf1 said:
Will I be able to still run AOSP Roms or will I have to stick with TW?
Click to expand...
Click to collapse
No you can still run AOSP roms, the only way you can lose MDK bootloader is if you flash firmware in Odin that is anything other than MDK, or if you take an OTA update while completely stock.
I guess I should say that after rooting stock MDK via towelroot, use a root explorer to delete SDM.apk and FWupgrade.apk from /system or /system/priv-app to prevent the phone from auto-updating before you flash a custom rom.
joshm.1219 said:
No you can still run AOSP roms, the only way you can lose MDK bootloader is if you flash firmware in Odin that is anything other than MDK, or if you take an OTA update while completely stock.
I guess I should say that after rooting stock MDK via towelroot, use a root explorer to delete SDM.apk and FWupgrade.apk from /system or /system/priv-app to prevent the phone from auto-updating before you flash a custom rom.
Click to expand...
Click to collapse
I'll definitely give it my best shot. Thank you!
Nwwolf1 said:
I'll definitely give it my best shot. Thank you!
Click to expand...
Click to collapse
Good luck, just letting you know, that full wipe tar file will wipe EVERYTHING. So make sure you have anything that you care about backed up on am external SD card or the cloud.
joshm.1219 said:
Good luck, just letting you know, that full wipe tar file will wipe EVERYTHING. So make sure you have anything that you care about backed up on am external SD card or the cloud.
Click to expand...
Click to collapse
Yeah I've got my music and photos backed up on my external SD and contacts backed with Google, those are really the only things I care about.
I was rooted and on hyperdrive rls19 and everything was ok accept the dialer would not switch calls on call waiting. Rls20 came out so I figured I would give it a shot maybe it would fix the issue. It didn't... So I asked a question about it in the hyperdrive help section. It was suggested to install a dialer app for touch wiz. which seemed to install but did nothing. So last night I bit the bullet and did a full wipe install of Hyperdrive. Which didn't go well. Could not get back into android. Constant app crashing and issues. Out comes Odin with a pit file and 4.4.2 flash. Seems like it is back to stock.
Now for the issues. towelrooted and grabbed twrp manager to install recovery. It will not install recovery. Everytime I try to get into recovery even holding down up home and power it just goes to downloading. I am so at wits end!!! Please help!
jspector said:
I was rooted and on hyperdrive rls19 and everything was ok accept the dialer would not switch calls on call waiting. Rls20 came out so I figured I would give it a shot maybe it would fix the issue. It didn't... So I asked a question about it in the hyperdrive help section. It was suggested to install a dialer app for touch wiz. which seemed to install but did nothing. So last night I bit the bullet and did a full wipe install of Hyperdrive. Which didn't go well. Could not get back into android. Constant app crashing and issues. Out comes Odin with a pit file and 4.4.2 flash. Seems like it is back to stock.
Now for the issues. towelrooted and grabbed twrp manager to install recovery. It will not install recovery. Everytime I try to get into recovery even holding down up home and power it just goes to downloading. I am so at wits end!!! Please help!
Click to expand...
Click to collapse
What build are you on? If it's anything after MDK, you can't install a custom recovery because of the locked bootloader. Your only option is Safestrap.
Sent from my NCC-1701 using Tapatalk.
riker147 said:
What build are you on? If it's anything after MDK, you can't install a custom recovery because of the locked bootloader. Your only option is Safestrap.
Sent from my NCC-1701 using Tapatalk.
Click to expand...
Click to collapse
vfrufnc5 I believe!
jspector said:
vfrufnc5 I believe!
Click to expand...
Click to collapse
Then your only option is Safestrap. No custom recoveries.
How did you install RLS 19? Were you MDK before you used Odin?
riker147 said:
Then your only option is Safestrap. No custom recoveries.
How did you install RLS 19? Were you MDK before you used Odin?
Click to expand...
Click to collapse
I used safestrap to install RLS19. The problem I was having is every time I went into recovery it would 1st go into the downloading screen. and I would have to power and down volume to get to reboot and goto safestrap. Did I maybe odin in the wrong version when I fixed it last night? I cannot get Bluetooth working today at all.
jspector said:
I used safestrap to install RLS19. The problem I was having is every time I went into recovery it would 1st go into the downloading screen. and I would have to power and down volume to get to reboot and goto safestrap. Did I maybe odin in the wrong version when I fixed it last night? I cannot get Bluetooth working today at all.
Click to expand...
Click to collapse
How are you trying to get into recovery? Pretty sure the only way to do that with Safestrap is through the app itself.
As far as your Bluetooth issues, I have no idea. What file did you flash with Odin?
riker147 said:
How are you trying to get into recovery? Pretty sure the only way to do that with Safestrap is through the app itself.
As far as your Bluetooth issues, I have no idea. What file did you flash with Odin?
Click to expand...
Click to collapse
Download: VRUFNC5 Full-Wipe SCH-I545_VZW_1_20140330160240_8il17ls9o2_fac.zip
MD5: 8a22dd4a47c2c5f890227fd952657d38
That is the file I flashed in odin with pit file. I am not sure what I was in before.
Hello all!
I recently flashed HyperDrive RLS 21 onto my s4, I originally had problems getting this to work on my phone. What I had to do was take my phone from it's NK1 kernel and flash it down to NC5 via Odin and then install HD and all modules. I then having trouble getting my stock ROM to run, I imagine this is due to the fact that it was now on NC5 and not it's natural NK1.
So what I did was flash it BACK to NK1 in order to retrieve my contacts. Upon rebooting and entering Safestrap then booting into my HD ROM slot, my phone got stuck on the Galaxy S4 boot logo. So I then tried wiping cache, this did nothing. So I then wiped data/factory reset in recovery mode then tried using Odin to put NK1 back on it. This has done nothing as I am still stuck on the boot logo.
I believe all I have to do is get back to Safestrap and factory wipe the HD ROM slot and reflash the stock ROM back to NC5.
Any help is appreciated!
Niotic said:
Hello all!
I recently flashed HyperDrive RLS 21 onto my s4, I originally had problems getting this to work on my phone. What I had to do was take my phone from it's NK1 kernel and flash it down to NC5 via Odin and then install HD and all modules. I then having trouble getting my stock ROM to run, I imagine this is due to the fact that it was now on NC5 and not it's natural NK1.
So what I did was flash it BACK to NK1 in order to retrieve my contacts. Upon rebooting and entering Safestrap then booting into my HD ROM slot, my phone got stuck on the Galaxy S4 boot logo. So I then tried wiping cache, this did nothing. So I then wiped data/factory reset in recovery mode then tried using Odin to put NK1 back on it. This has done nothing as I am still stuck on the boot logo.
I believe all I have to do is get back to Safestrap and factory wipe the HD ROM slot and reflash the stock ROM back to NC5.
Any help is appreciated!
Click to expand...
Click to collapse
Odin(Full Wipe) to nc5, then safestrap and do RLS21(with HyperdriveUI). I am on pure nc5 and I do weekly installs... and nc5 full wipes. You have to put the ROM in the stock slot, not any other slot.
XxD34THxX said:
Odin(Full Wipe) to nc5, then safestrap and do RLS21(with HyperdriveUI). I am on pure nc5 and I do weekly installs... and nc5 full wipes. You have to put the ROM in the stock slot, not any other slot.
Click to expand...
Click to collapse
What i ended up doing was using Kies to full wipe and upgrade to newest firmware (5.0.1). I believe I can just Odin down to NC5 now and do the entire rooting process over again then install HD into the stock slot.
Also, what do you mean when you say that you do weekly installs and full NC5 wipes?
Niotic said:
What i ended up doing was using Kies to full wipe and upgrade to newest firmware (5.0.1). I believe I can just Odin down to NC5 now and do the entire rooting process over again then install HD into the stock slot.
Also, what do you mean when you say that you do weekly installs and full NC5 wipes?
Click to expand...
Click to collapse
You may have already discovered this but you can't downgrade back to kk once you take the official lollipop upgrade
rrrrrrredbelly said:
You may have already discovered this but you can't downgrade back to kk once you take the official lollipop upgrade
Click to expand...
Click to collapse
I JUST now found this out! Well that sucks a lot. I didn't take the update via OTA but via Kies, I think I already know the answer here but does that change anything?
Niotic said:
I JUST now found this out! Well that sucks a lot. I didn't take the update via OTA but via Kies, I think I already know the answer here but does that change anything?
Click to expand...
Click to collapse
You're right, you already know the answer
rrrrrrredbelly said:
You're right, you already know the answer
Click to expand...
Click to collapse
Son of a gun, well I guess I will have to be patient
-_____-
Thanks anyways!
Niotic said:
Son of a gun, well I guess I will have to be patient
-_____-
Thanks anyways!
Click to expand...
Click to collapse
Patient for a downgrade method? Most likely will never happen. A physical qFuse has been blown.