Hey all,
* *Going to apologize in advance for a longer post, but I have a lot of questions I'm having a difficult time answering. Hope I'm posting in the correct forum too.
I'm on a Verizon GS4 (SCH-I545), 4.2.2. Build *JDQ39.I545VRUDML1. Presently Rooted and running Stock. (Based on horror stories I've been avoiding doing the update to the stock system)
I came from a Droid Bionic, and it was my first foray into rooting / modding Android phones, but I had it for 2.5 years and became quite proficient with what I could do with it. As a result, I've become very familiar with safestrap's touch screen. Before that I was capable of using bootstrap which used the type of recovery where I had to navigate it with volume keys.
So I have a series of questions that I can't get definitive answers for... More often than not when trying to flash ROMs I end up with a black screen and end up battery pulling and going back to stock system because I can't figure out why its happening.*
1. *Should I continue not taking the OTA update from verizon on my stock system? Most of the horror stories I hear about are with the ME7 build, but my present thinking is that the ML1 build is already past the ME7 one, so maybe all of the extra lockdown features are in place? I haven't been able to pin down exactly where I am on the build paths, and almost all custom ROMs are mentioning MDK or ME7, not really much mention of ML1 - I truly don't know exactly where I stand with this.
2. *Is it going to be easier in the long run if I just abandon safestrap and instead move to one of the other recoveries? I've read enough to understand that I need to flash the fix posted by Hashcode, although I don't really understand what the fix is doing, nor if I'm applying the correct fix. (the file I found was jfltevzw-ME7-modules.zip). Some of the other ROMs have specific fixes that I'm unsure what to do with, often using MDK or ME7 for the Radio. Again, since I don't really understand the differences between the builds, all I know is ME7 seems to be making it harder to flash ROMs. People have also said it doesn't matter if you're flashing the fix with the wrong name (IE I'm on ML1 but flashing the ME7 fix should still work... again not understanding exactly what it is is hurting me here).
* *2a. If I can/should stick with Safestrap, this is a side question - Are the ROMs usable in other slots than ROM slot 1? Throughout the life of my Bionic for the most part that was the only usable partition - most of the custom ROMs wouldn't work in other slots, is this still true?
3. *The only portion of success I've had is that I've had is with Hyperdrive. I've been able to flash this ROM fully and boot into it, but I've had no success with getting the wifi to work - a big problem since I'm not on unlimited data. I will post this specific question to the Hyperdrive thread itself to see if I can have someone help me, but all the research I've done on it has different people having different tricks that worked to get their wifi running (flashing the fix by queueing it after the ROM worked for some, canceling out before rebooting the ROM and separately flashing the Hashcode fix worked for others, one person even had to download the fix via their computer before transferring it to their phone in order for the fix to work - I've tried all of these things and still have no success with wifi).
I'm truly sorry if these questions have been answered before, but I have tried to look for the answers and there are just so many different specific ones I don't really know where I'm going wrong. I suspect there is a simple small detail that I'm doing which would make everything easier, such as using a different recovery, or that I''m flashing the wrong fix, etc. but I'm looking for a little advice to be able to have some success running these ROMs on my phone - After a week running the stock ROM, I'm already completely over it.
Thanks in advance for anyone that takes the time.
Sent from my SCH-I545 using Tapatalk
Quick update, I attempted to flash Bonestock on ROM slot 1 and was successful (previous attempts yielded black screens, but were all on ROM slot 2). I successfully got the ROM installed, but similar to Hyperdrive, I can get no wifi. Any attempt to turn it on yields the wifi flicking on for .25s before turning back off again.
Current assumption is that safestrap still wont load ROMs in other slots, but I still have no idea how to get wifi up and running.
Sent from my SCH-I545 using Tapatalk
I'm an idiot. Everywhere I put "ML1" I meant MI1. I've also determined via another howto YouTube video that MI1 is past ME7, so I am unsure if I should keep putting off OTAs, and also unsure if it will matter for my flashing customs.
Sent from my SCH-I545 using Tapatalk
Use MI1 modules not ME7 ones and flash the modules after you flash a rom. The black screen is normal give it ten minutes. Finally, Never, ever take an OTA.
Sent from my DROID RAZR using XDA Premium 4 mobile app
Found a post with the MI7 modules right before I checked back here and they worked like a charm. Now getting to look into some ROM goodness. Thanks much for the help!
Sent from my SCH-I545 using Tapatalk
Related
Ok, so I'm going to start by saying that I am the furthest thing away from being an android noob, but this is my first Moto android device. I can see right away in terms of rom and kernel flashing it's a bit different than all the other android devices I've owned. I Picked up a RAZR for a really good price and it came loaded with Safestrap and had a 4.2.2 AOKP nightly loaded already on it. KI'm completely unfamiliar with bootstrap and how it works (I plan on reading up and learning everything today), but the guy that gave it to me said he accidently deleted the stock rom. To me, coming from all htc devices, I didn't think that was a big deal because who wants stock anyways? So, I'm not sure if it's critical to get that stock rom loaded back on in one of the slots or not.
I guess the point of this post is to see if anyone would care to share a couple helpful pointers for a first time moto user and hopefully make this learning process a bit easier.
Thanks to anyone who takes the time to reply with something other than "Read the stickies"
If you are happy with the AOKP, no need to install stock ROM. Stock ROM probably have less bugs, working 1080 camcoder, but lack options, that AOKP has.
localceleb said:
Ok, so I'm going to start by saying that I am the furthest thing away from being an android noob, but this is my first Moto android device. I can see right away in terms of rom and kernel flashing it's a bit different than all the other android devices I've owned. I Picked up a RAZR for a really good price and it came loaded with Safestrap and had a 4.2.2 AOKP nightly loaded already on it. KI'm completely unfamiliar with bootstrap and how it works (I plan on reading up and learning everything today), but the guy that gave it to me said he accidently deleted the stock rom. To me, coming from all htc devices, I didn't think that was a big deal because who wants stock anyways? So, I'm not sure if it's critical to get that stock rom loaded back on in one of the slots or not.
I guess the point of this post is to see if anyone would care to share a couple helpful pointers for a first time moto user and hopefully make this learning process a bit easier.
Thanks to anyone who takes the time to reply with something other than "Read the stickies"
Click to expand...
Click to collapse
Next time, make sure dont to delete the stock ROM, you can install other custom ROM on other ROM slots, make your stock rom as a backup if anything happens.
If you want to go back to stock ROM, or if your razr is bricked, i suggest you to download the fastboot file and flash the xml.zip you downloaded using RSD lite from the PC. Its just the same as 'Odin' if youre Samsung user. Download the fastboot file in the link given and also download rsd lite,you can google for it
http://sbf.droid-developers.org/umts_spyder/list.php
Sent from my GT-I9300 using xda app-developers app
Carrier: Verizon
Device: Samsung Galaxy S4 (MK2)
Custom ROM: Hyperdrive ROM
Phone is rooted, and Safestrap is installed and working flawlessly
I see this question posted all the time, but I'm reading a lot of conflicting information. As I've been searching around the net for a solid (and up-to-date) answer, I was wondering if there was a definitive answer to the following question:
Can I flash a custom ROM to the stock slot using Safestrap, remove the stock ROM from the phone, and keep the backup on my PC for later restoration?
I would assume that I should do the following:
1) Make a backup of the stock ROM (using Safestrap)
2) Wipe the Stock slot
3) Install/Restore custom ROM to the Stock slot
Am I correct in assuming this?
If there are any issues, I'd love to hear why. I'm still trying to figure out all the info. If there are any benefits/drawbacks, I'd also love to hear those. I'd consider myself a "conservative" user. I do nothing with themes and major modifications.
Thank you for any advice!
I apologize if this question has been answered elsewhere.
That works just fine and many people already have. AT&T people are in the same boat and do it too.
Sent from Black<3's I337 running Foxhound ROM
DeadlySin9 said:
That works just fine and many people already have. AT&T people are in the same boat and do it too.
Sent from Black<3's I337 running Foxhound ROM
Click to expand...
Click to collapse
Thank you for the information.
remainnameless said:
Thank you for the information.
Click to expand...
Click to collapse
Just make sure you have the Odin tar file for your phone just in case something goes wrong. Me and a few others ran into some issues messing with the stock slot. Good idea to have that anyways.
Sent from my SCH-I545 using Tapatalk
Just in case someone comes across this in the future:
Everything worked as planned. No issues to report.
But doesn't this entirely contradict what the website says?
On the How-To Safestrap site:
Install: This is for flashing a .zip file to the currently active system. Currently, this is disabled for the stock system. In a future release I will enable flashing to the stock system.
Click to expand...
Click to collapse
And yet people are wiping and flashing to stock fine?
Cool, I will try that
Sent from my SCH-I545 using XDA Premium HD app
DaGamer12345 said:
But doesn't this entirely contradict what the website says?
On the How-To Safestrap site:
And yet people are wiping and flashing to stock fine?
Click to expand...
Click to collapse
Hashcode didn't support flashing to the stock slot when I used SafeStrap. You could do it, but if you ran into problems you were not to expect any help from him.
Now whether or not he disabled that option completely in newer versions of SafeStrap I'm not really sure since I'm on an mdk S4 now.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Hashcode didn't support flashing to the stock slot when I used SafeStrap. You could do it, but if you ran into problems you were not to expect any help from him.
Now whether or not he disabled that option completely in newer versions of SafeStrap I'm not really sure since I'm on an mdk S4 now.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
reason why its called safestrap...and has saved me many times able to get back to my stock rom slot...but we all have our own levels of risk but hashcode made safestrap the way he did for a reason.
I run 3 roms on my S4 and have no issues with memory limitations
So then this is a yes on flashing to stock? Thinking about flashing a SS rom, but not sure how it goes.
I assume I would flash the kernel modules as you have to do that with every custom rom.
If Safestrap lives on the stock system, how does it stay after you wipe? It stays on an unwipe-able area? Because it can't stay on recovery, can it?
If anything goes wrong, I could just flash the MK2 stock with Odin, correct? It wouldn't trip KNOX flag to 0x1?
Out of curiosity, if an OTA was available for stock MK2, and I had it as a custom rom, it would brick the phone or what would happen?
In Titanium Backup, you DON'T restore all the system apps, and only the user apps when migrating roms?
This would be my first time wiping/flashing a rom over the system (and not just over a rom slot), so I'm nervous as almost all people new to this sort of thing.
DaGamer12345 said:
So then this is a yes on flashing to stock? Thinking about flashing a SS rom, but not sure how it goes.
I assume I would flash the kernel modules as you have to do that with every custom rom.
If Safestrap lives on the stock system, how does it stay after you wipe? It stays on an unwipe-able area? Because it can't stay on recovery, can it?
If anything goes wrong, I could just flash the MK2 stock with Odin, correct? It wouldn't trip KNOX flag to 0x1?
Out of curiosity, if an OTA was available for stock MK2, and I had it as a custom rom, it would brick the phone or what would happen?
In Titanium Backup, you DON'T restore all the system apps, and only the user apps when migrating roms?
This would be my first time wiping/flashing a rom over the system (and not just over a rom slot), so I'm nervous as almost all people new to this sort of thing.
Click to expand...
Click to collapse
Well, you're asking a lot of questions that have been already answered, so here's some quick answers.
1. Flashing the modules won't hurt.
2. Safestrap lives in separate directory on your internal storage. As long as you don't wipe the internal storage, it'll still be there. However, if you flash a stock ROM into the stock slot, then Safestrap won't be run during boot and can't be activated.
3. Yes, you can always flash an OEM stock ROM. Factory images from Samsung won't set the Knox Warranty Void flag. This does NOT mean that you can downgrade to an earlier release.
4. OTAs won't brick the phone - they'll fail if you have modified anything that the OTA will be patching.
5. You should only restore user apps and data. You must have the restorecon fix for that to work. Restoring system apps is pretty risky.
None of these are new questions or new answers. Yes, there's a lot to read here, but you really need to spend the time.
k1mu said:
Well, you're asking a lot of questions that have been already answered, so here's some quick answers.
1. Flashing the modules won't hurt.
2. Safestrap lives in separate directory on your internal storage. As long as you don't wipe the internal storage, it'll still be there. However, if you flash a stock ROM into the stock slot, then Safestrap won't be run during boot and can't be activated.
3. Yes, you can always flash an OEM stock ROM. Factory images from Samsung won't set the Knox Warranty Void flag. This does NOT mean that you can downgrade to an earlier release.
4. OTAs won't brick the phone - they'll fail if you have modified anything that the OTA will be patching.
5. You should only restore user apps and data. You must have the restorecon fix for that to work. Restoring system apps is pretty risky.
None of these are new questions or new answers. Yes, there's a lot to read here, but you really need to spend the time.
Click to expand...
Click to collapse
Oh I remember you! You made the Saferoot method I used. Sorry for asking some dumb questions, I just wanted verification for 1, 3, and 4. I'll have to search for the restorecon fix. I'll be flashing Eclipse because I was only looking for an AOSP experience and Hyperdrive has more than I need (leading to larger rom size). The rom is going to go through a big update sometime this weekend so I'll wait for the update.
DaGamer12345 said:
Oh I remember you! You made the Saferoot method I used. Sorry for asking some dumb questions, I just wanted verification for 1, 3, and 4. I'll have to search for the restorecon fix. I'll be flashing Eclipse because I was only looking for an AOSP experience and Hyperdrive has more than I need (leading to larger rom size). The rom is going to go through a big update sometime this weekend so I'll wait for the update.
Click to expand...
Click to collapse
Whew. I thought "Oh I remember you" was going to be followed by ".. you're that jerk that... " :laugh:
Have a good weekend.
remainnameless said:
Carrier: Verizon
Device: Samsung Galaxy S4 (MK2)
Custom ROM: Hyperdrive ROM
Phone is rooted, and Safestrap is installed and working flawlessly
I see this question posted all the time, but I'm reading a lot of conflicting information. As I've been searching around the net for a solid (and up-to-date) answer, I was wondering if there was a definitive answer to the following question:
Can I flash a custom ROM to the stock slot using Safestrap, remove the stock ROM from the phone, and keep the backup on my PC for later restoration?
I would assume that I should do the following:
1) Make a backup of the stock ROM (using Safestrap)
2) Wipe the Stock slot
3) Install/Restore custom ROM to the Stock slot
Am I correct in assuming this?
If there are any issues, I'd love to hear why. I'm still trying to figure out all the info. If there are any benefits/drawbacks, I'd also love to hear those. I'd consider myself a "conservative" user. I do nothing with themes and major modifications.
Thank you for any advice!
I apologize if this question has been answered elsewhere.
Click to expand...
Click to collapse
I just installed hyperdrive to the stock slot and everything works perfect.
This is my first post on here and I may be out of place, but goin for it anyway. It's my understanding that Having a Verizon SCH-1545 with the MK2 build sucks. I started messing around with my phone without reading posts on here and feel lucky that I don't have an overpriced paperweight. I rooted my phone just because I could, it was fairly useful on other phones I had but the GS4 is already set up quite well. I wanted to flash to KitKat and talked to one of my friends who told me that he uses Slimkat. I now know that Rom Manager is pretty much useless on my phone and think that Hyperdrive through Safestrap is the only way I can flash my Rom. I attempted Cyanogenmod through CWM like an idiot because I'm impatient and it did not work and did not brick my phone. Before I try and install Hyperdirve I want to make sure that I have the right things. I downloaded Hyperdrive RLS 14 and am using Safestrap 3.71. I watched a video on installation through Safestrap from Rootjunky and he also installed a module with it, which I also downloaded. If someone can point me in the right direction to make sure that I do have everything I need and am doing this correctly, I would appreciate it. I have read several posts and tried to do the research but am a little confused. One of the things that worries me is when I boot my phone it says "safestrap: disabled". Did I do something wrong or is this because I'm still on the stock rom slot? I'm rambling now... Perhaps I should just leave it alone and not try to modify things out of boredom. Can I install just a kernel so that I can do some slight mods? Change my status bar, boot animation, etc...? Thanks for reading this short story and any help will be greatly appreciated.
Johnnyfriday said:
This is my first post on here and I may be out of place, but goin for it anyway. It's my understanding that Having a Verizon SCH-1545 with the MK2 build sucks. I started messing around with my phone without reading posts on here and feel lucky that I don't have an overpriced paperweight. I rooted my phone just because I could, it was fairly useful on other phones I had but the GS4 is already set up quite well. I wanted to flash to KitKat and talked to one of my friends who told me that he uses Slimkat. I now know that Rom Manager is pretty much useless on my phone and think that Hyperdrive through Safestrap is the only way I can flash my Rom. I attempted Cyanogenmod through CWM like an idiot because I'm impatient and it did not work and did not brick my phone. Before I try and install Hyperdirve I want to make sure that I have the right things. I downloaded Hyperdrive RLS 14 and am using Safestrap 3.71. I watched a video on installation through Safestrap from Rootjunky and he also installed a module with it, which I also downloaded. If someone can point me in the right direction to make sure that I do have everything I need and am doing this correctly, I would appreciate it. I have read several posts and tried to do the research but am a little confused. One of the things that worries me is when I boot my phone it says "safestrap: disabled". Did I do something wrong or is this because I'm still on the stock rom slot? I'm rambling now... Perhaps I should just leave it alone and not try to modify things out of boredom. Can I install just a kernel so that I can do some slight mods? Change my status bar, boot animation, etc...? Thanks for reading this short story and any help will be greatly appreciated.
Click to expand...
Click to collapse
you are lucky you didn't brick your phone, you really need to research more than you did
booting to stock rom slot is indicated by safestrap disabled message. If you creat a rom slot and install a safestrap compatible rom and set that slot active, the display will say safestrap enabled
http://forum.xda-developers.com/showthread.php?t=2606501
decaturbob said:
you are lucky you didn't brick your phone, you really need to research more than you did
booting to stock rom slot is indicated by safestrap disabled message. If you creat a rom slot and install a safestrap compatible rom and set that slot active, the display will say safestrap enabled
http://forum.xda-developers.com/showthread.php?t=2606501
Click to expand...
Click to collapse
I realized how big of a mistake I made when I hopped on to figure out why I was having problems. Since then have been trying to do hella research. Thanks for clearing up the Safestrap message.
Hi all... I did a bit of searching around but I'm still unsure of what to do, so forgive me because I'm sure this has been asked plenty of times and I know you all must be sick of seeing this question, but I just need to be sure so I don't mess anything up!
For the most part I haven't touched my S4 since I initially set it up. I'm still on MDK, CleanRom 1.6 (LOL) and still MDK. I've only updated recoveries on this phone (updated to the latest TWRP a week ago). Phone's on 4.2.2
I understand that MDK is too useful to lose so I have been very scared to play around with my phone and mess something up. I've always considered flashing various ROMs Ive found on this forum but never did it since I didn't wanna lose MDK.
So I guess what I'm trying to get at is how can I get my phone up to date modem/kernel/rom wise without messing anything up?
Again I apologize because I'm sure this gets asked all the time, but I appreciate any advice
Hovo said:
Hi all... I did a bit of searching around but I'm still unsure of what to do, so forgive me because I'm sure this has been asked plenty of times and I know you all must be sick of seeing this question, but I just need to be sure so I don't mess anything up!
For the most part I haven't touched my S4 since I initially set it up. I'm still on MDK, CleanRom 1.6 (LOL) and still MDK. I've only updated recoveries on this phone (updated to the latest TWRP a week ago). Phone's on 4.2.2
I understand that MDK is too useful to lose so I have been very scared to play around with my phone and mess something up. I've always considered flashing various ROMs Ive found on this forum but never did it since I didn't wanna lose MDK.
So I guess what I'm trying to get at is how can I get my phone up to date modem/kernel/rom wise without messing anything up?
Again I apologize because I'm sure this gets asked all the time, but I appreciate any advice
Click to expand...
Click to collapse
You would just flash a new ROM via TWRP, the same can be done with modems. I never touched the Kernel just stayed with whatever was baked into the ROM I flash.
You can view some ROMS on here http://forum.xda-developers.com/galaxy-s4-verizon/development ( I suggest Dan's GPE ROM) stable and smooth as hell.
You can also download and flash modems from here http://forum.xda-developers.com/showthread.php?t=2487298 (Flash MODEMS only)
By doing this you will not lose your MDK/Loki Hacked bootloader. Hope this helps. Oh yeah be sure to read and re-read those posts before doing anything. ;]
TY for the response!
I'm still a bit confused though. How do people end up losing their MDK bootloader then? Is it certain roms that they flash?
My previous phone was a Droid Charge where you had to flash to the stock version of Android that a certain ROM was on before you were able to flash that ROM so it's like a completely different process with S4's and it leaves me really puzzled lol.
Hovo said:
TY for the response!
I'm still a bit confused though. How do people end up losing their MDK bootloader then? Is it certain roms that they flash?
My previous phone was a Droid Charge where you had to flash to the stock version of Android that a certain ROM was on before you were able to flash that ROM so it's like a completely different process with S4's and it leaves me really puzzled lol.
Click to expand...
Click to collapse
Others can correct me if I'm wrong but I believe alot of people just end up taking the OTA update from Verizon which locks down their device.
People either have taken an OTA, or flashed a full image of a newer firmware in Odin. As long as you have an updated recovery, and flash a ROM meant for the vzw s4, you'll be good. You should go ahead and update your radios too.
circleofomega said:
plz..guys one small issur..some part of the system fonts are sudenly cyan-blue in colour??
whats this now??
Like...when i click on New contact: it asks me whatevr, where u want the new contact to be made and all, BUT here, on this screen, u see a "Select a contact type" < THIS HAS BECOME BLUE (cyan)
can any1 help me..i havent installed anything...
I stil have the Stock ROM..6.1...sorry Spikegotti to paste my doubt here..
Click to expand...
Click to collapse
Please do not update from MDK. I will trade you my S4.
Jesus loves you!
This is a Backup of the PH1 ROM's system and modem partitions. This is a Pre-Rooted ROM with the SD Card write permissions fix. This is different from my other post in those two differences.
You will need a custom recovery to install this ROM. (http://forum.xda-developers.com/note...lipop-t3089382)
Always perform the appropriate backups and other steps just in case something messes up. If you are on Lollipop, you should be able to just flash and go without any data loss (except custom system apps), but no promises.
Extract the folder (ES File Explorer or 7 Zipper) to "extsdcard/TWRP/backups/[serial number]" then boot into recovery and restore the image. The easiest way to get this folder is to simply perform a backup first, then unzip this folder next to the one for the backup you just created.
I didn't factory reset prior to this backup because it's just system partitions, so let me know if there's anything weird.
https://drive.google.com/open?id=0B2iEgzRTFjrQa2JEbE1DSE9qNHM
Here's the Odin ROM:
http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178/page1
Here's my non-rooted TWRP ROM:
http://forum.xda-developers.com/not...stom-recovery-rom-stock-rooted-t3449321/page1
Still 5.0 this is probably just a security update
RDF
http://device.sprintpcs.com/Samsung/SM-N900P-SPRINT/PH1.rdf
evilvoice said:
Still 5.0 this is probably just a security update
RDF
http://device.sprintpcs.com/Samsung/SM-N900P-SPRINT/PH1.rdf
Click to expand...
Click to collapse
Yep, just a security update most likely. Looks like some of the stock (Sprint) apps may have been updated as well . The update file was only about 190 megabytes if I remember correctly.
Quick question on updating modem & firmware.. I'm stock rooted ok2, and i dont have this update yet. I am working toward flashing the newly released and highly anticipated DL Modded N5N7 v4 which requires the PH1 updated firmware.
Do I need to ODIN flash the update files from the other PHI ROM thread or can I just do a full wipe and flash this backup with TWRP?
Thanks in advance.
Sent from my SM-N900P using XDA Labs
MeAtKeRtN said:
Quick question on updating modem & firmware.. I'm stock rooted ok2, and i dont have this update yet. I am working toward flashing the newly released and highly anticipated DL Modded N5N7 v4 which requires the PH1 updated firmware.
Do I need to ODIN flash the update files from the other PHI ROM thread or can I just do a full wipe and flash this backup with TWRP?
Thanks in advance.
Sent from my SM-N900P using XDA Labs
Click to expand...
Click to collapse
You can just flash the rom you want and keep your current bootloader/modem. But it's always suggested to keep current with any bootloader/modem, that the OP mentioned. That way if there is a issue with the install, it wouldn't be that.
Sent from my Nexus s using XDA-Developers mobile app
jhunt75 said:
You can just flash the rom you want and keep your current bootloader/modem. But it's always suggested to keep current with any bootloader/modem, that the OP mentioned. That way if there is a issue with the install, it wouldn't be that.
Sent from my Nexus s using XDA-Developers mobile app
Click to expand...
Click to collapse
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
MeAtKeRtN said:
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
Click to expand...
Click to collapse
Hey, I've seen you in a few threads and figured I ask before I made the same mistake. I'm looking to upgrade to DL Modded N5N7 v4 like yourself. I have a exploding Note 7 still and I'm anticipating being blacklisted at some point. As crazy as it sounds I like my Note 3's snappiness and everything else over the 7. My issue is my Note 7 radio gets 4g in my job and my Note 3 radio is 3g or spotty. I'm sure my modem and baseband is outdated and may help being updated
I'm on a older Moars Rom Baseband Nk4 android version 4.4.2. Did you figure out where things went bad. I was thinking of following these instructions http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178 don't want to mess this up.
What did you use and what should you have used?
Thanks
Lyvewire said:
Hey, I've seen you in a few threads and figured I ask before I made the same mistake. I'm looking to upgrade to DL Modded N5N7 v4 like yourself. I have a exploding Note 7 still and I'm anticipating being blacklisted at some point. As crazy as it sounds I like my Note 3's snappiness and everything else over the 7. My issue is my Note 7 radio gets 4g in my job and my Note 3 radio is 3g or spotty. I'm sure my modem and baseband is outdated and may help being updated
I'm on a older Moars Rom Baseband Nk4 android version 4.4.2. Did you figure out where things went bad. I was thinking of following these instructions http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178 don't want to mess this up.
What did you use and what should you have used?
Thanks
Click to expand...
Click to collapse
My mistake was following bad advice and flashing the TWRP Backup of PH1 in the OP of this thread instead of ODIN flashing the full ROM-ODIN-PH1- Update- t3463178.
I was able to get TWRP to restore my backup to OK2. From there I did a full wipe 3x and ODIN flashed the full PH1 update, immediately rooted with CFautoroot and reinstalled TWRP 2.8.7.0.
From there I followed the OP instructions in the DL Modded N5N7 thread which require the ROM, Kernel Cleaner, MVNO Buzbee2, Sprint VVM, and I installed the DL MM UIX Kernel.
The ROM and kernel are both really well put together except my mobile network connection to Sprint has been intermittent... the phone was stuck roaming and was connecting in spurts with Verizon, sprint, or the network was unavailable.
I just dirty flashed the Rom, Kernel, and MVNO fix an hour or so ago and the APNs seem to be sticking now. We'll see.
I have three Note 3's and each has its own quirky 'personality'- not especially playing nicely with most of the Port ROMs available these days. Hope this answers your questions and helps someone else trying to keep their Note 3 thriving.
MeAtKeRtN said:
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
Click to expand...
Click to collapse
I am not trying to start any trouble, but from reading your comment it seems you are suggesting I gave you bad or wrong advice. So I want to explain myself just in case it was a misunderstanding. All roms are capable of being flashed with older bootloaders and modems. But the proper thing to do, is to always be up to date with all bootloader/modem files. This way you will not run into any problems. Now I didn't mention anything about flashing the OP'S twrp backup method. I figured you may have been experienced enough to flash these BL/modem files from a source like sammobile. Then proceed to flash your rom of choice. As you experienced you lost your signal. It may have been a few reasons why this happen. 1. The way the OP mentioned to flash wasn't meant for your phone. Every phone response differently. 2. The rom for whatever reason can only be used if you dirty flashed over your current system. This will not be the only time you may have to do it this way. So instead of being sarcastic with your reply, maybe try and ask the one who is helping you to explain themselves more. We are all here to help each other, and by no means was my response to your question was meant to harm your phone.
Sent from my SM-N920C using XDA-Developers mobile app
jhunt75 said:
I am not trying to start any trouble, but from reading your comment it seems you are suggesting I gave you bad or wrong advice. So I want to explain myself just in case it was a misunderstanding. All roms are capable of being flashed with older bootloaders and modems. But the proper thing to do, is to always be up to date with all bootloader/modem files. This way you will not run into any problems. Now I didn't mention anything about flashing the OP'S twrp backup method. I figured you may have been experienced enough to flash these BL/modem files from a source like sammobile. Then proceed to flash your rom of choice. As you experienced you lost your signal. It may have been a few reasons why this happen. 1. The way the OP mentioned to flash wasn't meant for your phone. Every phone response differently. 2. The rom for whatever reason can only be used if you dirty flashed over your current system. This will not be the only time you may have to do it this way. So instead of being sarcastic with your reply, maybe try and ask the one who is helping you to explain themselves more. We are all here to help each other, and by no means was my response to your question was meant to harm your phone.
Click to expand...
Click to collapse
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
MeAtKeRtN said:
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
Click to expand...
Click to collapse
I never knew giving someone detailed information was a problem. It's funny how I never had an issue with the install, but you did. It seems you lack enough experience to realize a few things. But I will make it a point to never help you again. Whether that's to long-winded or not for you, oh well.
Sent from my SM-N920S using XDA-Developers mobile app
MeAtKeRtN said:
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
Click to expand...
Click to collapse
Did you get it all figured out?
I did get it figured out. Wasn't much more than an unnecessary inconvenience that someone else might be able to avoid.
Ok, so something weird...
Im running KK4.4.2 with the NC5 baseband on Sprint.
I upgraded my TWRP to 2.780 to flash the recovery both first time 'dirty flashing' and the 2nd time doing a facory wipe.
I removed the battery after the flash.
When I reboot, the phone stays on the Yellow Sprint screen and the LED pusles blue slowly. So far been doing it for 15 mintues.
What am I missing?
Dave
Unidave199 said:
Ok, so something weird...
Im running KK4.4.2 with the NC5 baseband on Sprint.
I upgraded my TWRP to 2.780 to flash the recovery both first time 'dirty flashing' and the 2nd time doing a facory wipe.
I removed the battery after the flash.
When I reboot, the phone stays on the Yellow Sprint screen and the LED pusles blue slowly. So far been doing it for 15 mintues.
What am I missing?
Dave
Click to expand...
Click to collapse
Give it 30 minutes? It seriously takes a long time. Are you sure you want to upgrade to lollipop? In just asking because you've been on Kit Kat long after support for lollipop or this phone has long stopped. I'd suggest downloading the latest Odin and flashing that instead, unless there is something here you wanted? I'm rooted on PL1 and have no issues other than my phone being as old as it is and how many times it's been flashed.
evilvoice said:
Give it 30 minutes? It seriously takes a long time. Are you sure you want to upgrade to lollipop? In just asking because you've been on Kit Kat long after support for lollipop or this phone has long stopped. I'd suggest downloading the latest Odin and flashing that instead, unless there is something here you wanted? I'm rooted on PL1 and have no issues other than my phone being as old as it is and how many times it's been flashed.
Click to expand...
Click to collapse
30 minutes? Woah that is a long time. Ok I will give it a try sometime when I go to bed.
I am mainly trying to get the PL1 update and not mess with Odin if I can get around it. I would like to try and port the Darklord Marshmellow ROM and take advantage of built in google assistant
So I thought I would try them. And always get back if I need to but wanted to keep the PL1 modem updates.
I only have one problem with one other phone user... She doesnt always get my texts and I dont always get hers. I dont know if others arent getting them and just dont know but my 1 friend I text a lot so she notices when there is a gap.
Anyways. Just feeling out how I can maximize this phone's performance. NO plans on changing phones anytime soon.
Unidave199 said:
30 minutes? Woah that is a long time. Ok I will give it a try sometime when I go to bed.
I am mainly trying to get the PL1 update and not mess with Odin if I can get around it. I would like to try and port the Darklord Marshmellow ROM and take advantage of built in google assistant
So I thought I would try them. And always get back if I need to but wanted to keep the PL1 modem updates.
I only have one problem with one other phone user... She doesnt always get my texts and I dont always get hers. I dont know if others arent getting them and just dont know but my 1 friend I text a lot so she notices when there is a gap.
Anyways. Just feeling out how I can maximize this phone's performance. NO plans on changing phones anytime soon.
Click to expand...
Click to collapse
I still use my note 3. Granted not for main phone as I switched to iPhone, but I use it every day. I don't really know the hesitation of using Odin, but to each their own. If you did decide to use Odin, I'd flash the ROM, boot it, go to download mode again, flash TWRP, boot recovery (so it sticks and doesn't go back to stock recovery), flash SuperSU, done. You're rooted on PL1. Hopefully you have already backed up your text messages and other various things to either SDCard or something else. I'm not sure if that survives whether you wipe and flash clean or Odin. Depending on provider, that could be your issue with text messages. If you're with Sprint, check that you are on latest PRL. If not, make sure APN settings are correct.
If you're only looking for Assistant, I had it running on stock PL1. XDA did a blog post about enabling it in Lollipop, so once you upgrade, check it out. I couldn't stay on Marshmallow. Being that these are ports and not specifically built for our phone, I ran into issue with every single ROM either not being able to place calls, text (MMS actually), or wireless/data not working. No matter what I changed APN to, I would always have issues. Some do not. I just can't recommend a port when they haven't worked for me. Some roms have been abandoned, which meant if I found one that I could at least handle, it was so outdated that it was unusable (issues had arisen and the developer had moved on so they weren't being fixed). By handling a rom, I mean that after I upgraded to iPhone, I only needed wireless to work (to connect to hotspot) and it not go into a boot loop or crash all the time (some do). Those roms I have no idea if calls or text work because I wasn't using that. A lot have issues with wireless working.
One more thing you can try is to do a flash, wait about 30 minutes. If it still doesn't boot, pull the battery and reboot into recovery. Wipe data and cache and reboot again. It should boot. It'll still take a long time. Make sure you wait the 30 minutes before pulling the battery (it should have finished upgrading your system by then). Do note that first boot from now on will take forever no matter if it's a port or stock. Lollipop and higher take a long time to upgrade. I've only had 1 or 2 roms take around 5 minutes and that's because they were minimalist and without Google apps. The phone does get a little warm and uses a lot of battery, so I'd keep it plugged in.
Please report back if you got it to work and how. Like I said, I still use mine. I still visit this forum every day even though I've had an s5 and an s7 edge. I love this phone. I need to get mine replaced because I've worn it out: broken charger port so I have to make sure the cable is plugged in a certain way and I can't touch the phone while charging, side molding is broken off in places, some of my partitions can't be changed which means the memory is failing (not even Odin flashes correctly anymore let alone custom roms). But, it still keeps on ticking.
evilvoice said:
I still use my note 3. Granted not for main phone as I switched to iPhone, but I use it every day. I don't really know the hesitation of using Odin, but to each their own. If you did decide to use Odin, I'd flash the ROM, boot it, go to download mode again, flash TWRP, boot recovery (so it sticks and doesn't go back to stock recovery), flash SuperSU, done. You're rooted on PL1. Hopefully you have already backed up your text messages and other various things to either SDCard or something else. I'm not sure if that survives whether you wipe and flash clean or Odin. Depending on provider, that could be your issue with text messages. If you're with Sprint, check that you are on latest PRL. If not, make sure APN settings are correct.
If you're only looking for Assistant, I had it running on stock PL1. XDA did a blog post about enabling it in Lollipop, so once you upgrade, check it out. I couldn't stay on Marshmallow. Being that these are ports and not specifically built for our phone, I ran into issue with every single ROM either not being able to place calls, text (MMS actually), or wireless/data not working. No matter what I changed APN to, I would always have issues. Some do not. I just can't recommend a port when they haven't worked for me. Some roms have been abandoned, which meant if I found one that I could at least handle, it was so outdated that it was unusable (issues had arisen and the developer had moved on so they weren't being fixed). By handling a rom, I mean that after I upgraded to iPhone, I only needed wireless to work (to connect to hotspot) and it not go into a boot loop or crash all the time (some do). Those roms I have no idea if calls or text work because I wasn't using that. A lot have issues with wireless working.
One more thing you can try is to do a flash, wait about 30 minutes. If it still doesn't boot, pull the battery and reboot into recovery. Wipe data and cache and reboot again. It should boot. It'll still take a long time. Make sure you wait the 30 minutes before pulling the battery (it should have finished upgrading your system by then). Do note that first boot from now on will take forever no matter if it's a port or stock. Lollipop and higher take a long time to upgrade. I've only had 1 or 2 roms take around 5 minutes and that's because they were minimalist and without Google apps. The phone does get a little warm and uses a lot of battery, so I'd keep it plugged in.
Please report back if you got it to work and how. Like I said, I still use mine. I still visit this forum every day even though I've had an s5 and an s7 edge. I love this phone. I need to get mine replaced because I've worn it out: broken charger port so I have to make sure the cable is plugged in a certain way and I can't touch the phone while charging, side molding is broken off in places, some of my partitions can't be changed which means the memory is failing (not even Odin flashes correctly anymore let alone custom roms). But, it still keeps on ticking.
Click to expand...
Click to collapse
Come back to Android! We miss you!!!!
Yes I am backed up and also have a Titanium Backup of everything so I am pretty much covered... I have even backed up the backups to my PC!
You have much wisdom in what you are saying. I thought I would play around with some other ROM's and see what the potential is.
I hear good things about the Darklord Reborn by Midevil and JCorderno so thought I would investigate.
I am not opposed to using Odin, but I was at work, and no access to a computer so wanted to see if I could do the upgrade 'on the fly' since I am already rooted and with recovery.
Man, waiting 30 minutes for a phone to boot sounds like a anxiety attack waiting to happen! But still wanna give it a try.
As to your USB port. Have you thought of going wireless charging? I did and haven't looked back! You can get a wireless charging back and a case that will fit at...
for the charging back
https://smile.amazon.com/Samsung-Ga...=8-2&keywords=samsung+note+3+wireless+charger
for the case
https://smile.amazon.com/gp/product/B00F3KP156/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
Clone Wars....
Just wanted to put out a big THANKS for this.. I broke my Note 3 after 2,433 days (long story) but had bought a stock spare on Ebay last year... Making the switch now, but your PH1 Flashable update is making it super easy!
To let everyone who needs to use this nowdays... you will need to Flash an older TWRP (I used 2.7.8) in order to allow the Modem partition to be overwritten. Then you can flash up to 3.x to load a Android 10 based rom.