Edit: They do keep coming!
I looked into doing it, and there is no way in hell that I should be a) doing it, and b) unleashing it onto the world. It would be bad.
I only have the one phone to test it on and can't risk messing it up and I don't have the experience to work on it if it didn't come out perfectly.
I expect that it will be the last Sprint ROM released for this phone, We're nearing the end of support, so it would be good to have these final versions "fixed" and available
...on the off chance a few developers will jump right in and cook up a few mega ROMs for us.
DQG1 Root and Xposed (rewritten)
On a related note, I installed stock DQA1 DQG1, using the usual CF Autoroot, battery pull thingy process Odin for the ROM and TWRP, then booting once, booting into recovery, and then installing SuperSU and it rooted fine. No loss of settings or anything else as far as I can tell.
I did have to install the latest versions of the Xposed files. After rooting and custom recovery (TWRP works fine), install XposedInstaller_3.1.4.apk first like any other apk, then go to recovery and install Wanam v87.1-alt-sdk23-arm-custom-build, but everything (Xprivacy, etc.) worked fine. Keep in mind, you HAVE to use the "alt" (see the "alt" in the file name above?) version or else it won't work. Samsung made some changes, blah, blah, blah. Much thanks to Wanam!
New side note: I did do a factory wipe, and even after reinstalling everything, and using a ROM that contains bloatware, I still have like 40% more space on the phone. I truly don't know what happened there.
Anyone have any thoughts as to kernel? I downloaded Emotion r26 RC1, and BeastModeKernel 1.0BETA, but I haven't tried them yet.
EDIT: Emotion r26 RC1 works fine, but it doesn't seem like CPU freqs are ever going to stick.
No surprise that neither Emotion nor BeastModeKernel worked; I haven't seen anything else that may.
Thoughts anyone?
Both kernels are good, emotion has a few more options to tweak but I took an update a month or two ago and run NotEdge ROM fine , I just use SO launcher with it because I like TW, also latest xposed is 86.1 and I wish I could do what your asking but it probably would be just as bad you'll be fine with that ROM I just suggested it has everything u just requested just make a nandroid and do it at home in case you do something wrong you can always ODIN back your firmware
Sent from my HTC One M9 using XDA-Developers mobile app
D'oh!!
Eating a little crow here. So far, there have been two three 742 updates, maybe there will be more. Who knows?
But I edited the title of the first post. Again. Again. 741 times.
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Over a year later, and the still keep coming.
Hmmmm.
I did take another gander around, but it seems that I would need Linux to do it correctly, so I am still opting out of doing it myself.
mictek said:
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Click to expand...
Click to collapse
They all arrive here: https://www.sammobile.com/firmwares/galaxy-note-edge/SM-N915P/ eventually.
Hello i got a note 4 Sprint MM 6.0.1 N910PVPU5DQI5 . i am from Argentina, and i bought the phone used from a guy from USA. (i don`t know how but it`s working with the bands here but i dont know if 4g is working, the guy says it works, maybe i don`t have 4g singal in my zone) .
the phone works fine, but has some srpint stuff and ads that bother me. so i flashed TWRP , and now i am looking for any roms and kernels to flash.
for example, is safe to flash this: https://forum.xda-developers.com/note-4-sprint/development/rom-updated-1-14-2017-t3538051
or should i change something first ???.
Related
OK so ive figured some things out, you probably know them, thats not what i made this thread for.
xhausx s-on kernel installer will not install a kernel if going from JB to Sense.
And for some reason, if coming from PA 2.99, with the latest 2.1 komodo rls 21, HTC dumlock will not let you get back to sense either...
Trying to go back to mean rom at the moment and it has taken me a couple hours lol, its rediculous, thought i could do it without fastboot, or flash image gui, and i was wrong. So i started looking around, found out it was a buck, then i found this forum.
http://forum.xda-developers.com/showthread.php?t=1772769
Thought it might be a tad helpful, it contains the apk for flash image gui at the right version for our phone.
Enjoy and have a wonderful day.
Woot.
got back mean rom aparantly a big issue was with the v6.5 release of meanrom. put 6.4 on there and it worked just fine.
Still tho, a free Flash Image GUI a big plus. So check it out.
Though joeykrim offers his app free thru the forum, it is a good gesture to purchase it for a $1 to show support for such a great tool. It saves a lot of headache for many.
Sent from my EVO using Tapatalk 2
I haven't had issues with the kernel installer on meanrom and I switch between sense and aosp quite often. Dumlock should always work because recovery is flashed into the boot partition essentially replacing boot and allowing twrp to flash the kernel directly. I don't see how it would fail.
If anyone can confirm the jb/kernel installer issue or provide a log from it I should be able to fix it. I haven't tested it yet with 4.2 JB but unless they changed something major it should still work the same.
Many devs provide their tools for free on here, but as mentioned by one_love_420 please show your support and get the donate version if it's something you feel is worthy of it. A lot of hard work goes into some of these apps.
Indeed
xHausx said:
If anyone can confirm the jb/kernel installer issue or provide a log from it I should be able to fix it. I haven't tested it yet with 4.2 JB but unless they changed something major it should still work the same.
Many devs provide their tools for free on here, but as mentioned by one_love_420 please show your support and get the donate version if it's something you feel is worthy of it. A lot of hard work goes into some of these apps.
Click to expand...
Click to collapse
I was just throwing it out there for those who wanted the link, just saw it was a buck on the app store and was looking around to see if it supported our phone yet (last i had checked the one on the app store didnt) a quick google search told me it did and provided me a free link, so just sharing.
I also wanted to say that,
When coming from the original PA (not lens flares) to Super LTE which had the s-on kernel installer, super lte would get stuck in a boot loop. And then when going from PA (lens flares) with the rls 21 komodo kernel, to mean rom (latest) it wouldnt boot, so i just went with what i knew and stated it couldnt, tho i havnt attempted to reproduce the effect since as i am currently sticking with mean rom. You would not believe the fear i had when i couldnt boot my phone for a while and couldnt find out why, then upon trying to unroot using the latest RUU to simply quick fix the problem, the RUU gave me an error, lol i thought my phone was gone.
But it ended up being a problem with mean rom, i went back to PA and then used the dumlock to install an older version of mean rom and all was well.
om4 said:
I haven't had issues with the kernel installer on meanrom and I switch between sense and aosp quite often. Dumlock should always work because recovery is flashed into the boot partition essentially replacing boot and allowing twrp to flash the kernel directly. I don't see how it would fail.
Click to expand...
Click to collapse
Oh and i totally agree with you, i know how the dumlock works and i didnt see what the problem could be at the time, it was just a problem with the latest release of mean rom, flashed and got stuck at the white HTC screen and being s-on that ment i couldnt use the dumlock anymore or anything for that matter. so i was flippin out trying to find the problem before the obvious hit me. I just had assumed with mean rom always being so stable that the newest release wouldnt have bothered my phone. Guess i was wrong though, still have no idea whats wrong with it but that version of mean rom still wont install and work lol. Its all good though, this post might as well serve as a quick shot to a link that you may or may not have known was there.
I'm not sure what I did but I never had any trouble recovery back to sense till now. Every other time I've flashed from job to sense it hasn't been a problem. I have tried Meanrom 6.5, and stock.goodies. with no luck. When I try to flash the boot.IMG, the button is grey out and won't let me flash.
I'm stumped.
Sent from my EVO using Tapatalk 2
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software. I ended up giving up and just kept pushing the OTA off. It got so bad that I decided last night to install a recovery and then flash an unofficial CWM rom. So this morning it was working fine and then all of the sudden, I lost VZW data. Couldn't get any signal. So I decided to try to flash the Official Cyanogenmod 11. That blew up during the setup and gave me an error that it could not find any cellular service. I wiped the phone and tried to restore the backup I made of my stock rom with the recovery on it. I made the backup the second the recovery was finished. It's giving me an MD5 error?? I've tried this multiple times with the same result. So, I then decide to flash one of the two roms (unofficial & official) back to see if I can get the phone working again. No such luck.... It keeps trying to set up my "cellular service" and just runs. Nothing ever finishes. I'm really worried at this point. I would be perfectly fine to flash a Verizon image and go back to stock. But I can't seem to find out how to do this or where to find the file. Please help me.. I'm getting desperate.
Edit: I tired to flash the Unofficial Rom again and this time it seems to be working. I would still rather just go back to stock though. If anyone can point me to the correct place I'd be very appreciative.
Thanks
Dave
dbow32 said:
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software. I ended up giving up and just kept pushing the OTA off. It got so bad that I decided last night to install a recovery and then flash an unofficial CWM rom. So this morning it was working fine and then all of the sudden, I lost VZW data. Couldn't get any signal. So I decided to try to flash the Official Cyanogenmod 11. That blew up during the setup and gave me an error that it could not find any cellular service. I wiped the phone and tried to restore the backup I made of my stock rom with the recovery on it. I made the backup the second the recovery was finished. It's giving me an MD5 error?? I've tried this multiple times with the same result. So, I then decide to flash one of the two roms (unofficial & official) back to see if I can get the phone working again. No such luck.... It keeps trying to set up my "cellular service" and just runs. Nothing ever finishes. I'm really worried at this point. I would be perfectly fine to flash a Verizon image and go back to stock. But I can't seem to find out how to do this or where to find the file. Please help me.. I'm getting desperate.
Edit: I tired to flash the Unofficial Rom again and this time it seems to be working. I would still rather just go back to stock though. If anyone can point me to the correct place I'd be very appreciative.
Thanks
Dave
Click to expand...
Click to collapse
Here is a link to flash back to stock: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
I know you wanted to take the OTA, but why not download one of the stock based 11c ROM's, like Jasmine 3.0? That way you'll still get the latest version(11c) but you won't lose root and recovery. The OTA patches root, so no recovery either. Here's a link for Jasmine 3.0 stock based 11c if you want to try it: http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
Also, there has been issues with data on the CM builds. It seems pretty common right now. Check the CM threads for more info on that. I believe there is a command people have been entering(killall rild in terminal emulator) to get data back, but it seems 50/50 that it'll work.
startswithPendswithOOH said:
Here is a link to flash back to stock: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
I know you wanted to take the OTA, but why not download one of the stock based 11c ROM's, like Jasmine 3.0? That way you'll still get the latest version(11c) but you won't lose root and recovery. The OTA patches root, so no recovery either. Here's a link for Jasmine 3.0 stock based 11c if you want to try it: http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
Also, there has been issues with data on the CM builds. It seems pretty common right now. Check the CM threads for more info on that. I believe there is a command people have been entering(killall rild in terminal emulator) to get data back, but it seems 50/50 that it'll work.
Click to expand...
Click to collapse
Hey thanks a lot for your reply. I understand what you're saying with going back to stock. My issues with flashing custom Roms is that I have to have my phone work 100%. I've been flashing since the original Droid Incredible. And I've NEVER found a Rom that didn't have minor glitches and issues. Usually those issues affect my daily routine. I'll give Jasmine3.0 a shot and if it works I might just keep it. If not i'll just suffer through VZW's BS! Anyway, really appreciate your input.
Dave
dbow32 said:
Hey thanks a lot for your reply. I understand what you're saying with going back to stock. My issues with flashing custom Roms is that I have to have my phone work 100%. I've been flashing since the original Droid Incredible. And I've NEVER found a Rom that didn't have minor glitches and issues. Usually those issues affect my daily routine. I'll give Jasmine3.0 a shot and if it works I might just keep it. If not i'll just suffer through VZW's BS! Anyway, really appreciate your input.
Dave
Click to expand...
Click to collapse
Glad to help. I'm with you on the 100% functionality too, so that is why I'm on Jasmine 3.0. Don't get me wrong, I love custom ROMs and all the work the devs do, but until all the kinks are worked out I'd rather be stock.
Also, I'm not trying to advertise anything, but flashing the skydragon kernel into Jasmine has helped the speed/lag and battery life as well. Its worth a try - but it only works on stock/non-AOSP based ROMs. If you try it though, also download the stock 11c kernel that the OP put in the thread just in case you have issues. I don't have the link handy, but the kernel is located in the "original android development" thread. Peace
dbow32 said:
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software.
Click to expand...
Click to collapse
Which drivers were you using? I had trouble with the Unified Drivers linked in some posts and had to use the Verizon specific drivers. I also had to usually reinstall the drivers each time I tried to use the flash tool to get it to recognize my phone.
BladeRunner said:
Which drivers were you using? I had trouble with the Unified Drivers linked in some posts and had to use the Verizon specific drivers. I also had to usually reinstall the drivers each time I tried to use the flash tool to get it to recognize my phone.
Click to expand...
Click to collapse
To be honest, I'm not sure what drivers I was using. I did a Google search for LG suite and found the closest version I could find. They didn't have the VS985, Only P985. So that might have had something to do with it.
startswithPendswithOOH said:
Glad to help. I'm with you on the 100% functionality too, so that is why I'm on Jasmine 3.0. Don't get me wrong, I love custom ROMs and all the work the devs do, but until all the kinks are worked out I'd rather be stock.
Also, I'm not trying to advertise anything, but flashing the skydragon kernel into Jasmine has helped the speed/lag and battery life as well. Its worth a try - but it only works on stock/non-AOSP based ROMs. If you try it though, also download the stock 11c kernel that the OP put in the thread just in case you have issues. I don't have the link handy, but the kernel is located in the "original android development" thread. Peace
Click to expand...
Click to collapse
I have a question, what is the "Modem" for? BTW, this Rom is VERY nice. Thanks
dbow32 said:
I have a question, what is the "Modem" for? BTW, this Rom is VERY nice. Thanks
Click to expand...
Click to collapse
Modem is the radio. Some people reported better signal strength on the 11c modem versus the 10b modem, but I didn't notice too much of a difference myself.
And glad you like the ROM, but all thanks go to hsbadr who came up with it
startswithPendswithOOH said:
Modem is the radio. Some people reported better signal strength on the 11c modem versus the 10b modem, but I didn't notice too much of a difference myself.
And glad you like the ROM, but all thanks go to hsbadr who came up with it
Click to expand...
Click to collapse
You know, it's really odd but the last few weeks my phone's signal has dropped. I listen to Sirius through my phone during the day at work. And I've always received 1 to 2 bars of 4g. But the last few weeks, It's dropped to about 2 to 3 bars of 3G. I thought maybe VZW was secretly throttling me. But maybe it's the updated Radio?
dbow32 said:
You know, it's really odd but the last few weeks my phone's signal has dropped. I listen to Sirius through my phone during the day at work. And I've always received 1 to 2 bars of 4g. But the last few weeks, It's dropped to about 2 to 3 bars of 3G. I thought maybe VZW was secretly throttling me. But maybe it's the updated Radio?
Click to expand...
Click to collapse
It's possible the modem could've been causing problems. Is 11c better or worse for you? And its also possible big red was throttling you too. That seems like something they'd do.
If you use/like xposed framework G3 tweaksbox is a good app to get for customizing your phone a little bit. And greenify and amplify are good xposed apps that help your battery life a whole lot. They are worth checking out in the play store.
Hello,
I have an issue with making a tweaked, modified, etc TouchWiz ROM (aka BaconOS).
When I debloated, deodexed, deknoxed it with Assayed kitchen (and by flashing a debloat/deknox zip before that), the WiFi stopped working for some reason.
So I tried deodexing and only removing some apps (file manager, camera, samsung store, email, gapps), but that didn't fix the issue.
After that, I tried flashing stock ROM (Nothing changed, extracted using ext4unpacker) with assayed kitchen's updater-script, but still nothing.
Please let me know how to fix this issue.
maybe replace wifi folder from very stock rom..?
Naksuhd said:
maybe replace wifi folder from very stock rom..?
Click to expand...
Click to collapse
It has to do something with deodexing, because when I deodexed the stock rom, wifi stopped working. So the ROM will be odexed (a bit slower)
tried with odex system, problem is with debloating..
Hi, are you seriously making a ROM for this old device? Wow, finally something at last!
Had this device since christmas of 2014 and actively used it as my main device until january 2017.
During this time, I rooted it about 6 times. A couple of times I did it with Kingroot (or was it Kingoroot?) and all was well. But every time I tried to root using a SuperSU root that I found here, there was this glitch that would seemingly trigger out of nowhere, causing infinite "App has closed unexpectedly" messages to appear, along with a black screen behind those warnings, nothing worked until I did a factory reset. Yea, frustrating times...
I have always wondered why nobody bothered to port literally anything to this phone. Not even a (working) custom recovery was ever available for it. There was one that I tried, but was very unsuccessful in trying to boot it.
All that being said, my phone's battery has unfortunately "gone up in size", or "spicy pillow", so I can't really test anything right now.
My phone is the SM-G357FZ running TMZ firmware (Czech republic T-Mobile), and I always wanted to get rid of that and put an unbranded European CSC/firmware onto it.
I support you in your efforts OP and can't wait to test out your work!
Edit: I just discovered that there was an official update released by Samsung in 2021! Have you considered basing your ROM on that instead of the now ancient 2017 ROM?