I was running eclipse 4.2.2 and spent two days flashing Vario's Roms and modems
I ended up going back to eclipse 4.2.2 and now every time I run a system process my phone freezes. Black screen. Sometime reboots.
I was doing full wipes or data/cache/davlik every time.
I can't figure it out. Pressing volume up or down freezes and lags the phone.
Pressing the phone icon lags and submitting the call lags the phone.
On top of that my mp3s on my sdcard no longer work on Google music...
Any idea how to fix this? My phone is almost useless except for third party apps. Thanks
gt5oh said:
I was running eclipse 4.2.2 and spent two days flashing Vario's Roms and modems
I ended up going back to eclipse 4.2.2 and now every time I run a system process my phone freezes. Black screen. Sometime reboots.
I was doing full wipes or data/cache/davlik every time.
I can't figure it out. Pressing volume up or down freezes and lags the phone.
Pressing the phone icon lags and submitting the call lags the phone.
On top of that my mp3s on my sdcard no longer work on Google music...
Any idea how to fix this? My phone is almost useless except for third party apps. Thanks
Click to expand...
Click to collapse
Give us more info.. I take it you are mdk with loki exploit...right?
safestrap enabled, Hyperdrive driven
decaturbob said:
Give us more info.. I take it you are mdk with loki exploit...right?
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
Mdk correct. Loki
I'm using cwm recovery
Volume up and down is also bogging down the phone..
Been messing with this for hours
No matter what rom I run the core system is messed up
I ODIN back to stock.
What happens if I accept the stock OEM software upgrade?
gt5oh said:
Been messing with this for hours
No matter what rom I run the core system is messed up
Click to expand...
Click to collapse
Have you considered odin the stock mdk full wipe image file to start over?
safestrap enabled, Hyperdrive driven
decaturbob said:
Have you considered odin the stock mdk full wipe image file to start over?
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
yeah I did that, im on stock mdk 4.2.2 right now, software update popped up, if I take it will I be able to root in the future?
gt5oh said:
yeah I did that, im on stock mdk 4.2.2 right now, software update popped up, if I take it will I be able to root in the future?
Click to expand...
Click to collapse
Root yes. Custom recovery, no. Your only option would be Safestrap and compatible TW roms. Try to do whatever it takes to stay on MDK.
Sent from my NCC 1701 using Tapatalk 4
riker147 said:
Root yes. Custom recovery, no. Your only option would be Safestrap and compatible TW roms. Try to do whatever it takes to stay on MDK.
Sent from my NCC 1701 using Tapatalk 4
Click to expand...
Click to collapse
ok got it thanks.. is there a stock but rooted mk2 rom that you can install from mdk with CWM?
gt5oh said:
ok got it thanks.. is there a stock but rooted mk2 rom that you can install from mdk with CWM?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2581072
There's a stock rooted MK2 ROM you can flash in CWM. Just don't take that OTA!
Sent from my SCH-I545 using Tapatalk
gt5oh said:
yeah I did that, im on stock mdk 4.2.2 right now, software update popped up, if I take it will I be able to root in the future?
Click to expand...
Click to collapse
if you are mdk, I would NEVER take OTA as that will cause you to lose custom recoveries and ability to rom any type of ROM and custom kernels. There is a way to continue forward with MDK but I don't know what the process is as I don't have MDK myself
Yes I rejected the update.
Instead I put on CWM recovery and flashed the TW stock 4.3 build
Was running Eclipse 4.2.2 before
Related
So I wasn't thinking when I first got my s4 and figured the update was just something small but now that I look on here it looks like that update was definitely something big... What does this mean for me? Can I not run custom roms or kernels now?
That is correct. Currently you can root but you cannot install a custom recovery. Without a custom recovery you cannot install different roms or kernels. You cannot odin back to MDK. Hashcode is fine tuning a workaround using Safestrap, but it is not available yet. You can follow his progress here
http://forum.xda-developers.com/showthread.php?p=45185924
jaxon01 said:
That is correct. Currently you can root but you cannot install a custom recovery. Without a custom recovery you cannot install different roms or kernels. You cannot odin back to MDK. Hashcode is fine tuning a workaround using Safestrap, but it is not available yet. You can follow his progress here
http://forum.xda-developers.com/showthread.php?p=45185924
Click to expand...
Click to collapse
Okay thanks for the info. I used safestrap and it seemed to work well on my droid razr do you know the difference between using safestrap and using normal recovery, I'm just curious.
fatmando2 said:
Okay thanks for the info. I used safestrap and it seemed to work well on my droid razr do you know the difference between using safestrap and using normal recovery, I'm just curious.
Click to expand...
Click to collapse
custom recovery replaces your normal recovery, allowing you to overwrite the whole system when flashing a rom
safestrap keeps the stock software, and boots a recovery on top of it, keeping the stock software while kind-of dual booting your own ROM.
Or at least i think this is how it works in a layman's term.
JaeKay said:
custom recovery replaces your normal recovery, allowing you to overwrite the whole system when flashing a rom
safestrap keeps the stock software, and boots a recovery on top of it, keeping the stock software while kind-of dual booting your own ROM.
Or at least i think this is how it works in a layman's term.
Click to expand...
Click to collapse
Ok, are there reasons why one is better then the other or are they just different methods of doing the same type of thing?
fatmando2 said:
Ok, are there reasons why one is better then the other or are they just different methods of doing the same type of thing?
Click to expand...
Click to collapse
safestrap wont ever really brick your phone, but you got double the storage for system files
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 installed Safestrap onto my GS4 in hopes of installing a ROM to get ride of touchwiz. I found a safestrap compatible ROM and installed it through safestrap. Now I cant boot into the system. I wiped all data and cache and factory setting. When ever I restart, sometimes it says: [Safestap: Disabled] or [Safestrap: enabled] I can access recovery. I tapped continue on both and just doesn't work.
Bit of a noob so dont be too hard
EDIT: I Installed Hyperdrive successfully until the end. Its at this screen: Beginning Android OS 4.3 boot sequence... .... .... ...." It has stayed here for hours, all night. Should I take out the battery? Buttons don't work
High_Rez said:
I installed Safestrap onto my GS4 in hopes of installing a ROM to get ride of touchwiz. I found a safestrap compatible ROM and installed it through safestrap. Now I cant boot into the system. I wiped all data and cache and factory setting. When ever I restart, sometimes it says: [Safestap: Disabled] or [Safestrap: enabled] I can access recovery. I tapped continue on both and just doesn't work.
Bit of a noob so dont be too hard
Click to expand...
Click to collapse
So you created a rom slot and flashed the rom to that slot? What build base are you..why SS version did u use and rom did u flash ...?
Sent from my SCH-I545 using XDA Premium 4 mobile app
decaturbob said:
So you created a rom slot and flashed the rom to that slot? What build base are you..why SS version did u use and rom did u flash ...?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I created the rom slot. Im MK2, I used safestrap because I have a locked BL. Whats SS? I used a ROM called Barebone Stock.
When ever I flash a rom, all that happens when I restart is it says safestrap: Disabled or enabled. I choose recovery every time because rebooting doesnt do any thing.
High_Rez said:
I created the rom slot. Im MK2, I used safestrap because I have a locked BL. Whats SS? I used a ROM called Barebone Stock.
When ever I flash a rom, all that happens when I restart is it says safestrap: Disabled or enabled. I choose recovery every time because rebooting doesnt do any thing.
Click to expand...
Click to collapse
SS is SafeStrap but you should try to uninstall the rom and reboot into stock and then go back and try to reinstall the rom
Sent from my SCH-I545 using Tapatalk
High_Rez said:
I created the rom slot. Im MK2, I used safestrap because I have a locked BL. Whats SS? I used a ROM called Barebone Stock.
When ever I flash a rom, all that happens when I restart is it says safestrap: Disabled or enabled. I choose recovery every time because rebooting doesnt do any thing.
Click to expand...
Click to collapse
SS = abreviation for safestrap, thought that was pretty obvious
barebone ROM? Im not familar with that one being SS compatible. The safestrap disabled msg on display means the stock rom slot is active and the phone should boot to stock. When you have rom loaded into a rom slot 1 or 2 or whatever, you must "activate" that slot for it to boot. I would suggest deleting the rom slot you made and start over.
decaturbob said:
SS = abreviation for safestrap, thought that was pretty obvious
barebone ROM? Im not familar with that one being SS compatible. The safestrap disabled msg on display means the stock rom slot is active and the phone should boot to stock. When you have rom loaded into a rom slot 1 or 2 or whatever, you must "activate" that slot for it to boot. I would suggest deleting the rom slot you made and start over.
Click to expand...
Click to collapse
So I made a 3rd rom slot and installed hyperdrive. everthing went well until the end. Its at this screen that says "Beginning Android OS 4.3 boot sequence...." Its been on this screen for hours. All night
High_Rez said:
So I made a 3rd rom slot and installed hyperdrive. everthing went well until the end. Its at this screen that says "Beginning Android OS 4.3 boot sequence...." Its been on this screen for hours. All night
Click to expand...
Click to collapse
So, let's start from the basics - you're not telling us what versions of anything that you're using.
First, what build is your phone? i.e. the stock slot.
What version of Safestrap are you trying to use?
What version of Hyperdrive are you trying to flash?
When the phone hangs like that during boot, something critical has crashed that's preventing the boot.
You're booting Android 4.3 according to the above, so you should be flashing using SS 3.71 on build MJ7 or MK2 and Hyperdrive RLS14.
If all that is correct: the build is MJ7 or MK2, the Safestrap is 3.71, and you're trying Hyperdrive RLS14, then the likely cause is that you have a bad download. Check the md5sum after downloading to ensure that it's OK. Download it to your PC, not directly to the phone, then check the MD5 before transferring it to your sdcard and flashing it.
k1mu said:
So, let's start from the basics - you're not telling us what versions of anything that you're using.
First, what build is your phone? i.e. the stock slot.
What version of Safestrap are you trying to use?
What version of Hyperdrive are you trying to flash?
When the phone hangs like that during boot, something critical has crashed that's preventing the boot.
You're booting Android 4.3 according to the above, so you should be flashing using SS 3.71 on build MJ7 or MK2 and Hyperdrive RLS14.
If all that is correct: the build is MJ7 or MK2, the Safestrap is 3.71, and you're trying Hyperdrive RLS14, then the likely cause is that you have a bad download. Check the md5sum after downloading to ensure that it's OK. Download it to your PC, not directly to the phone, then check the MD5 before transferring it to your sdcard and flashing it.
Click to expand...
Click to collapse
My buld is MK2
The The SS version is: it doesnt say. But is says TWRP v2.6.3.1.
Im using hyperdrive RLS14 S4.zip
I have my SD in my PC and I downloaded it from the forum to it. then flashed it. Also I think I screwed up stock because i cant access the system. I cant boot into it.
High_Rez said:
My buld is MK2
The The SS version is: it doesnt say. But is says TWRP v2.6.3.1.
Im using hyperdrive RLS14 S4.zip
I have my SD in my PC and I downloaded it from the forum to it. then flashed it. Also I think I screwed up stock because i cant access the system. I cant boot into it.
Click to expand...
Click to collapse
OK, If your stock slot is damaged, you probably need to re-flash and start over.
Download the MK2 "No-Wipe" rom image from this thread and flash it using ODIN 3.09 - that'll get you back to stock, Then try the Safestrap stuff again. Seems like you have the right versions of things, so if you follow the directions, it should boot OK.
Be sure to check the MD5 of anything you download. There's free software available that does that.
k1mu said:
OK, If your stock slot is damaged, you probably need to re-flash and start over.
Download the MK2 "No-Wipe" rom image from this thread and flash it using ODIN 3.09 - that'll get you back to stock, Then try the Safestrap stuff again. Seems like you have the right versions of things, so if you follow the directions, it should boot OK.
Be sure to check the MD5 of anything you download. There's free software available that does that.
Click to expand...
Click to collapse
Do I need to worry about any root?
High_Rez said:
Do I need to worry about any root?
Click to expand...
Click to collapse
Yeah after you flash the image in Odin use the saferoot guide that k1mu posted to obtain root again.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
k1mu said:
OK, If your stock slot is damaged, you probably need to re-flash and start over.
Download the MK2 "No-Wipe" rom image from this thread and flash it using ODIN 3.09 - that'll get you back to stock, Then try the Safestrap stuff again. Seems like you have the right versions of things, so if you follow the directions, it should boot OK.
Be sure to check the MD5 of anything you download. There's free software available that does that.
Click to expand...
Click to collapse
I just dont see why I need to restart every thing. Is there any other possible way?
High_Rez said:
I just dont see why I need to restart every thing. Is there any other possible way?
Click to expand...
Click to collapse
Well is your stock slot still working? If u just messed up a ROM slot than you can erase them and start over.
But if it was your stock slot then using Odin probably is the only thing that will help you.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Well is your stock slot still working? If u just messed up a ROM slot than you can erase them and start over.
But if it was your stock slot then using Odin probably is the only thing that will help you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Ok. Thanks
High_Rez said:
Ok. Thanks
Click to expand...
Click to collapse
Are you all set now?? Sounds to me like you messed up the stock slot from what I could gather from earlier posts.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Are you all set now?? Sounds to me like you messed up the stock slot from what I could gather from earlier posts.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Odin is not reading my phone. Yeah, all i need to do it flash the original firmware and root it and start over. But i dont see how that could work.
High_Rez said:
Odin is not reading my phone. Yeah, all i need to do it flash the original firmware and root it and start over. But i dont see how that could work.
Click to expand...
Click to collapse
I heard that you need to use the cord that came with the phone when you got it. So make sure you are and also try another USB port.
Sent from my SCH-I545 using Tapatalk
High_Rez said:
Odin is not reading my phone. Yeah, all i need to do it flash the original firmware and root it and start over. But i dont see how that could work.
Click to expand...
Click to collapse
Well you probably just need the USB drivers for your phone that's all. I just went through that myself with my new laptop. I ended up just googling it and finding the right ones.
It will work for you, once your back to stock just use Saferoot again, then install SafeStrap again... Then be certain whatever ROM u flash is SafeStrap compatible. I'd say use ROM slots for the time being until your more comfortable with things.... Don't take that the wrong way... Just saying is all. Messing with the stock slot can lead you back to where you're at right now that's all.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 03:19 PM ---------- Previous post was at 03:17 PM ----------
Try the drivers that k1mu has in his saferoot thread
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Well you probably just need the USB drivers for your phone that's all. I just went through that myself with my new laptop. I ended up just googling it and finding the right ones.
It will work for you, once your back to stock just use Saferoot again, then install SafeStrap again... Then be certain whatever ROM u flash is SafeStrap compatible. I'd say use ROM slots for the time being until your more comfortable with things.... Don't take that the wrong way... Just saying is all. Messing with the stock slot can lead you back to where you're at right now that's all.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 03:19 PM ---------- Previous post was at 03:17 PM ----------
Try the drivers that k1mu has in his saferoot thread
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I found the drivers but they say its already installed on my computer.
High_Rez said:
I found the drivers but they say its already installed on my computer.
Click to expand...
Click to collapse
Reinstall them then restart your computer
Sent from my SCH-I545 using Tapatalk
On my sch-i545 how do I go about getting the newest safestrap or whatever is the best of that so that I can utilize the newest rpms such as Hyper drive rom?
Thanks.
Do some research...there are stickies and threads on it
Sent from my GT-P5110 using XDA Premium 4 mobile app
decaturbob said:
Do some research...there are stickies and threads on it
Sent from my GT-P5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My research has netted me a phone that is stuck in a boot loop.
Followed this: http://forum.xda-developers.com/showthread.php?t=2726868
and installed Hyperdrive RLS15, however it is stuck on a constant reboot
How can I fix this? How can I verify that the upgrade from mk2 to nc2 went perfectly? odin claimed it passed when I wrote the files as said in the thread.
When its trying to boot up I see the safestrap, then nothing appears on the screen. It vibrates twice, and starts over again.
and for some reason it will delete the slot 1 I setup and installed this in and force itself back to the stock rom slot.
I am using safestrap 3.72 though
I also noticed under stock rom slot, my system partition size is 0MB O_O my data partition size is 9970mb and cache is 2040mb. Something went wrong here?
Someone please help. Thanks.
Ok after MUCH more reading. I downgraded back to mk2, and now I'm able to get started on my nc2 rooting and rom installing. I think I figured it out. Somehow I got a 3.72 version of safestrap and that messed me up.
ElementalWindX said:
My research has netted me a phone that is stuck in a boot loop.
Followed this: http://forum.xda-developers.com/showthread.php?t=2726868
and installed Hyperdrive RLS15, however it is stuck on a constant reboot
How can I fix this? How can I verify that the upgrade from mk2 to nc2 went perfectly? odin claimed it passed when I wrote the files as said in the thread.
When its trying to boot up I see the safestrap, then nothing appears on the screen. It vibrates twice, and starts over again. and for some reason it will delete the slot 1 I setup and installed this in and force itself back to the stock rom slot.
I am using safestrap 3.72 though
I also noticed under stock rom slot, my system partition size is 0MB O_O my data partition size is 9970mb and cache is 2040mb. Something went wrong here?
Someone please help. Thanks.
Click to expand...
Click to collapse
hyperdrive 15 will not run on nc2 if you upgraded your bootloader to NC2 which is 4.4....where in that link did it talk about loading hyperdrive? SS 3.72 is for 4.4, safestrap versions are tied to basebuilds and as far as I know, not backwards compatible.
right now there aren't really any custom ROMs you can load into safestrap 3.72/NC2/NC5 except perhaps echo.....all the other discussions are for stock kitkat rom
decaturbob said:
hyperdrive 15 will not run on nc2 if you upgraded your bootloader to NC2 which is 4.4....where in that link did it talk about loading hyperdrive? SS 3.72 is for 4.4, safestrap versions are tied to basebuilds and as far as I know, not backwards compatible.
right now there aren't really any custom ROMs you can load into safestrap 3.72/NC2/NC5 except perhaps echo.....all the other discussions are for stock kitkat rom
Click to expand...
Click to collapse
That's what I was afraid of. idk why I had it in my head that rls15 was meant for kitkat.
Wish the rom makers would catch up
ElementalWindX said:
That's what I was afraid of. idk why I had it in my head that rls15 was meant for kitkat.
Wish the rom makers would catch up
Click to expand...
Click to collapse
Rom makers do so on their free time with very few users even bothering to do any donations if at all...
sent by safestrap enabled bajarom
So much goes into making a ROM it's amazing some of the devs even do it. Just shows how much they love this stuff
Sent from my SCH-I545 using Tapatalk
Mistertac said:
So much goes into making a ROM it's amazing some of the devs even do it. Just shows how much they love this stuff
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yea I agree.
It's ****ty the actual big corporations won't make it EASIER for them, instead of locking boot loaders and just being an all around pita about it.
So right now the all around best bet is to stay on mk2 these days?
ElementalWindX said:
Yea I agree.
It's ****ty the actual big corporations won't make it EASIER for them, instead of locking boot loaders and just being an all around pita about it.
So right now the all around best bet is to stay on mk2 these days?
Click to expand...
Click to collapse
For a while. Until some more 4.4 ss compatible roms are available
sent by safestrap enabled bajarom
ElementalWindX said:
Yea I agree.
It's ****ty the actual big corporations won't make it EASIER for them, instead of locking boot loaders and just being an all around pita about it.
So right now the all around best bet is to stay on mk2 these days?
Click to expand...
Click to collapse
Well I'd personally stay on mk2 just to have more options rom wise and not have to do the Odin juggling act from mk2 to nc5 or vice versa but that's just me
Sent from my SCH-I545 using Tapatalk
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.