Related
Hello,
I was able to root my SGSII GT-I9100T using Clockworkmod. I then proceeded to flash Android KitKat but during that procedure, my phone displayed an error with the emmc (or something like that) and the installation was aborted. I can get onto the Recovery screen but I can't get any further, i.e. I can't get to my apps, messages etc.
I do not have a backup of prior to the error in the flash. The top of the screen I am able to see says: CWM-based Recovery v6.0.1.2-Siyah. I have wiped my data and cache with no luck. Everytime I reboot, it goes back to the same screen.
Also, I am with Vodafone Australia, and they do not appear to have a downloadable stock ROM.
I want to get my phone back to prior to rooting, obviously with the default settings (but this doesn't matter).
What should I do? Am I able to repair it?
Yes, you're able to repair it easily. If you don't have any backup, doing a wipe from recovery (which can sometimes fix this) isn't an option for you because obviously you'll lose data if you wipe. I'm also thinking perhaps you've flashed the wrong version of Siyah; you could always re-read (or read) the Siyah threads on here to make doubly sure you've flashed the correct build for your Android version (I don't remember which is which, been ages since I've used Siyah), and if it is a case of you having flashed the wrong build, flashing the right build might well solve your problem & give you a rooted phone. You could also find the PhilZ thread on here, read it, and flash that which should also help you to achieve that aim.
But...if you really want to go back to where you were before you started...
Download a stock rom for Voda AU from Samfirmware (Doesn't matter which one, up to you. You'll need to sign up in order to do so), and flash it following the instructions in the thread titled 'Flash Stock firmware/ROM...' stickied near the top of Q&A.
If you're unable to get a successful Odin flash/or it fails for whatever reason, find Hopper8's 'Odin troubleshooting' guide stickied in the General section & try the stuff in that thread, which should enable you to get through any issues & get a successful Odin flash which will take your phone back to the state it was in before you attempted to root it.
Normally flashing a one part stock rom like this won't involve data loss, but there are never any water-tight guarantees.
Edit - For future reference, if you ever decide to mod your phone even slightly, always back everything up before you do anything. Don't be like the 95% of people on here who do this & then end up in the **** because they didn't back stuff up. The reality is, if you're going to mod, stuff goes wrong eventually for everyone (as you've just found out).
Thank you, I will attempt to flash a stock from that website.
Just to clarify, I first installed CWM (not the Siyah version), and that was working fine. I was able to boot and do whatever. I then proceeded to flash an Android KitKat ROM but this resulted in an error. I then flashed Siyah (which may have made it worse) because from what I read at the time, it could have fixed my problem. So it must have been from the ROM, whether it be my phone being not compatible with it etc., rather than the wrong version of Siyah (although, as I said before, it could have made it worse).
Yep, rom incompatibility. Siyah stopped being developed with ICS, so won't work with KK roms; kernels need to be compatible with the Android version of the rom in question.
Doing what you did is no drama usually, worst case result is normally what happened to you I.E bootloop which won't go away without going back to stock, unless you get a bad flash. It's actually a good learning experience, because now you'll know how to recover if you flash stuff in future
I managed to flash the stock version and thankfully, my phone is back to 'normal'. Luckily I always had intentions on resetting it to factory settings. Indeed it has been a good learning experience :good: Thanks for your help, MistahBungle.
No worries. Glad you got it sorted
(I had included all links to the zips and files I used but XDA wouldn't let me include those due to this being my first post.)
I need help. I messed up pretty bad. I have a Galaxy S3 T999N on Metro Pcs. A buddy got me into root about a year ago. It's been slow for me, because I'm scared of bricking my device. (I've read many guides, forum posts and watched many videos but I've never had the courage to flash a custom ROM, even though it looks really fun.)
SPECS
Galaxy S3 T999N 4.2.1 on Metro Pcs
The phone was rooted with Odin 3.07.
Later I used Odin 3.09 to flash custom recovery for TWRP. (Zip: openrecovery-twrp-2.3.1.1-d2mtr)
A couple days ago, I finally got enough courage to flash a custom rom. I Used titanium to back up all my apps, then used twrp to make a restore.
I used TWRP on the nightly I found (cm-11-20140217-NIGHTLY-d2mtr.zip). It failed. I apologize for not doing a log dump... I can't remember exactly what the log said. Something like (ERROR 7 or STATUS 7)
I wiped the cache and dalvik cache and used the recovery I made before the attempt at cyanogen, then I wiped the cache and dalvik cache again. TWRP said it was a successful recovery. When I went to reboot into the stock OS... It just hangs at the "Metro PCS Wireless for all" intro screen.
I started to do research on that symptom. found all kinds of threads on boot loops.
I tried leaving the battery out for 30 seconds, then booting into twrp to wipe the cache several times.
Then I tried the same steps with the dalvik included.
Then I repeated that same process with a factory reset. (several times.) Always the same result.
I even tried that entire process with wiping the entire phone, DATA, cache, dalvik, system, then doing recovery again. Doesn't work.
My recovery isn't working. I don't know what to do. (ALSO, INTERESTING SYMPTOM: I've noticed after doing the recovery, during the boot, the part when the black with white font Galaxy splash screen plays, the sound that it makes when the blue galaxy animation forms... it sounds like that sound starts late and gets cut off, then it sticks at the "Metro PCS Wireless for all" intro screen. It only does this after a factory reset, it doesn't make any sound at all otherwise because I think my phone's sound was turned off when I made the restore.)
I had a tech buddy try to find my stock rom, he wasn't sure which one to use. (confusion between Metro pcs and T-mobile S3s discussed below.) He told me to try another custom rom. If I could get one to work, that means the phone is still good and the custom rom would give me time to possibly find the stock rom for my model. (I just paid my bill, I'm wasting service right now.)
First I tried to find a stock rom for my phone. If I used "metro pcs" as a part of the google search, it came back with mostly results pertaining to Samsung Galaxy S III SCH-R530M (I've owned the SCH-R530M... it was white and the first model variant that Metro PCS had. I think it was only 4G not 4GLTE) All I could find for the T999N is a T-Mobile stock 4.1 but my device is 4.2. and on metro PCS. I was told that when the device updated to 4.2, partitioning and other things changed on the device specific to a 4.2 setup. So if I tried to use a 4.1 stock rom I could brick my device. (In the reading I've done, I've never came across anything that said that on the internet.)
So I moved on and started looking for another custom rom. I had seen a lot of videos on pacman. Looks awesome. After doing some reading, I found pacman on the android forums. (pac_d2mtr-20130510-v22.1.1)
IT WORKED! I was super excited. I got this X-mas-ish feeling in my stomach, like I just opened an awesome gift.
The Wifi Worked, but the camera, DATA and calls did not work. I was still super excited! First I explored Pacman, and ended up in the about phone section. (Model number was SCH-R530M! This probably isn't going to function the way I'd like, I thought to my self.)
The more I played with pac's interface, the more it kept freezing. Had to do a bunch of battery pulls.
On the same thread mentioned above, There was some talk about MMS problems, someone suggested flashing this for 4g and MMS fixes. (AOKP TO METRO FIX.zip) using TWRP, It flashed successfully but didn't fix my calls or DATA.
BY THIS TIME, IT WAS LATE, HAD BEEN READING FOR HOURS AND I WAS FEELING TIRED AND REALLY BUMMED.)
Then I tried to look for my models modem files to flash. (I'll be honest, I'm new to this, I had no idea where to look.) eventually I found a modem repostiory on a thread(Can't find the site in my history, but I found the link) I found this: USC_T999N_GalaxyS3_UVBNC1_Modem. I flashed that, it didn't work either.
At that point, I think I flashed AOKP TO METRO FIX.zip and USC_T999N_GalaxyS3_UVBNC1_Modem.zip out of panic and frustration of not having a phone. Could I have messed up my radios? is it possible that even if I ever get back into my stock, could the radios be messed up now cause I flashed AOKP TO METRO FIX.zip and USC_T999N_GalaxyS3_UVBNC1_Modem.zip?
I'm scared... and burned out. I really need a phone and don't have money for an insurance deductible or a new phone. (I know... what a stupid noob, right?)
I hate my current job and have been on the hunt for about three months, which paid off with a couple interviews. I'm waiting for 2nd interviews to be scheduled. How will they or anyone else interested in
hiring me, reach me?
A lot of the threads I've read, people report that their device can't boot into recovery or boot into download mode. MINE CAN STILL DO BOTH.
I'm not sure what to do. I appreciate anyone who took the time to read all of this.
TO SUM IT ALL UP, I WAS WONDERING:
1. Is there another method how to fix the boot loop problem?
2. I also heard that T-Mobile and Metro PCS merged, which is why I have a T-Mobile model. Would it matter if I used the T Mobile Stock (or custom rom.) When technically I'm on Metro PCS?
2a. Would that effect my ability to make calls?
3. Also, is it true that using a 4.1 stock rom after having taking the 4.2 update, will that brick my Phone?
3a. Is there a place that offers 4.2 stock roms? I could only find 4.1 (not sure where to look.)
3b. My wife has the exact same phone, same model, rooted, only hers is 4.1 and mine is 4.2 - Could there be a method or some useful way to use the firmware from the wife's phone?
4. Is it possible that if I ever get back into my stock, could the radios be
messed up now cause I flashed AOKP TO METRO FIX.zip and USC_T999N_GalaxyS3_UVBNC1_Modem.zip while messing with pacman?
5. My phone can still go into download mode and it still boots into recovery. Is there any hope that I can save this? What else do I need to consider? Is all my network settings stuck on the recovery?
THANK YOU FOR YOUR TIME.
Hi. I bought a near-mint S4 on Swappa from a seller who had already rooted it and installed a custom ROM (one similar to Samsung stock). After verifying that it worked I did a factory wipe, deleted the caches and used the existing TW recovery to install CM11, which so far I just love -- it's extremely close to the stock Android on my Nexus tablet, only with other great options like running Titanium backup and a firewall, etc. The lack of VZW and Samsung bloat is also great, of course.
However, do I need to worry that the phone could still be infected with or vulnerable to malware, perhaps because of something left over from whatever process the seller used to root the phone and install recovery? Would using the Avast firewall protect me, or would I be wiser to unroot the phone, take it back to stock and start all over again? (I'm reluctant to do that because it has the MK2 baseband and I'm afraid of not being able to get back to having a custom recovery.) Am I worrying needlessly, because the willing and installation of CM would have deleted any dangerous stuff that may have been lurking?)
This is my first time dealing with a rooted phone or a custom ROM. I really like the idea of having more control over what I run on my own phone (similar to running Linux on my computers, which I've been doing for years), but want to make sure I'm not being foolish somehow.
Aquifer122 said:
Hi. I bought a near-mint S4 on Swappa from a seller who had already rooted it and installed a custom ROM (one similar to Samsung stock). After verifying that it worked I did a factory wipe, deleted the caches and used the existing TW recovery to install CM11, which so far I just love -- it's extremely close to the stock Android on my Nexus tablet, only with other great options like running Titanium backup and a firewall, etc. The lack of VZW and Samsung bloat is also great, of course.
However, do I need to worry that the phone could still be infected with or vulnerable to malware, perhaps because of something left over from whatever process the seller used to root the phone and install recovery? Would using the Avast firewall protect me, or would I be wiser to unroot the phone, take it back to stock and start all over again? (I'm reluctant to do that because it has the MK2 baseband and I'm afraid of not being able to get back to having a custom recovery.) Am I worrying needlessly, because the willing and installation of CM would have deleted any dangerous stuff that may have been lurking?)
This is my first time dealing with a rooted phone or a custom ROM. I really like the idea of having more control over what I run on my own phone (similar to running Linux on my computers, which I've been doing for years), but want to make sure I'm not being foolish somehow.
Click to expand...
Click to collapse
Since you're able to run CM11, it must be running the MDK build, which is pretty amazing as you can run what you want with the Loki exploit allowing you to bypass the locked bootloader.
If you really are concerned about what's on the phone, you can always flash a full-wipe factory MDK ROM image and start over.
DO NOT - Don't - no - never- take any factory updates. Or flash anything past MDK from Verizon. Ever.
Thank you -- I do indeed feel fortunate about having the MDK build and don't want to do anything to mess it up.
How reasonable are my concerns about some vulnerability being left on the phone by the prior owner? I did two wipes of the phone (system, data, cache and dalvik cache each time) before installing CM.
Aquifer122 said:
Thank you -- I do indeed feel fortunate about having the MDK build and don't want to do anything to mess it up.
How reasonable are my concerns about some vulnerability being left on the phone by the prior owner? I did two wipes of the phone (system, data, cache and dalvik cache each time) before installing CM.
Click to expand...
Click to collapse
You'll be fine if you hop into recovery and do a Factory Reset where it includes the Internal Card.
Most likely your all set though with what you've done. Enjoy that MDK phone! I also have one and being able to run non Touchwiz Roms is the only way to go if you ask me.
If you have anymore questions regarding MDK feel free to hit me up or ask here... Were all here to help
Sent from my SCH-I545 using Tapatalk
As the title says, I'd like to flash Ditto Note 3 ROM v5.2. I am currently running Alliance ROM build 26 with TWRP 2.7.2.0.
What I'm looking for is a basic step-by-step (I feel pretty confident about finding detailed breakdowns of each step so please don't put yourself out too much--I'll follow up if there's anything I don't understand) so that there's nothing I miss, leaving me with a bricked phone, a locked bootloader that I can't revert, or non-functional radio/modem/anything.
I'm fine with ODIN, flashing, recovery, and other basics. I'm really just looking for each step that is ABSOLUTELY REQUIRED in order to not run into the problems mentioned above. I'd like to be able to get back to where I'm at now in case I decide I don't care for DN3. Thank you in advance.
I've attached a screenshot of "About Phone" in case the info helps.
I've also never taken an OTA or used an OFFICIAL stock ROM except for the one it came with, I rooted and unlocked as soon as it was possible after day one of release with no updates/upgrades prior (pre-ordered from Verizon, first ROM was BeansTown build 1 ).
Is what I'm asking possible? Can this be done without relocking the bootloader?
Applejackson said:
As the title says, I'd like to flash Ditto Note 3 ROM v5.2. I am currently running Alliance ROM build 26 with TWRP 2.7.2.0.
What I'm looking for is a basic step-by-step (I feel pretty confident about finding detailed breakdowns of each step so please don't put yourself out too much--I'll follow up if there's anything I don't understand) so that there's nothing I miss, leaving me with a bricked phone, a locked bootloader that I can't revert, or non-functional radio/modem/anything.
I'm fine with ODIN, flashing, recovery, and other basics. I'm really just looking for each step that is ABSOLUTELY REQUIRED in order to not run into the problems mentioned above. I'd like to be able to get back to where I'm at now in case I decide I don't care for DN3. Thank you in advance.
I've attached a screenshot of "About Phone" in case the info helps.
I've also never taken an OTA or used an OFFICIAL stock ROM except for the one it came with, I rooted and unlocked as soon as it was possible after day one of release with no updates/upgrades prior (pre-ordered from Verizon, first ROM was BeansTown build 1 ).
Is what I'm asking possible? Can this be done without relocking the bootloader?
Click to expand...
Click to collapse
Since you are already using Alliance B26 (an MJ9 based ROM), you shouldn't need to use ODIN for anything.
I simply followed the instructions in the DN3 post, and I was up and running w/o issues.
I'm not sure about TWRP, bc I used the latest version of Philz myself, and had no issues. I've heard of some people not having issues with TWRP, and others who did. Seems like YMMV, based on all the posts I've gone through in that thread (you should go through it yourself and get an idea).
Also, I am having the odd lockup every so often with this ROM (I believe it is deep sleep based), which a few others are also experiencing. Outside of that, I love the ROM too.
Thanks for the reply.
devious_z said:
Since you are already using Alliance B26 (an MJ9 based ROM), you shouldn't need to use ODIN for anything.
I simply followed the instructions in the DN3 post, and I was up and running w/o issues.
I'm not sure about TWRP, bc I used the latest version of Philz myself, and had no issues. I've heard of some people not having issues with TWRP, and others who did. Seems like YMMV, based on all the posts I've gone through in that thread (you should go through it yourself and get an idea).
Also, I am having the odd lockup every so often with this ROM (I believe it is deep sleep based), which a few others are also experiencing. Outside of that, I love the ROM too.
Click to expand...
Click to collapse
Thanks for taking the time. I guess my main concern was with the bootloader and whether or not I had to upgrade it and possibly lock it accidentally, or if I could just stay with the bootloader I have now, which is actually VRUEMJB. Used the method outlined in the AllianceRom thread for flashing the ROM. Since I still have a virgin bootloader I didn't want to lock it. I think I'll just try flashing the ROM as I have it, after a wipe of course, and I can always flash a recovery backup if need be.
I did try looking through the info in the threads for the ROM, but there are thousands of pages on the original and 90+ in the [**UPDATED] Verizon DN3 thread. The ones that I have read through have some conflicting information, so this query is really just to eliminate any confusion on my part before changing anything I can't change back.
Update: Tried and failed.
Just an update, I tried with my current configuration as I said I would above. Factory Reset, Data Format, the whole nine yards, and everything seems to go smoothly until the final reboot after everything is installed. The phone just hangs on the Samsung boot image and never goes any further. Tried reinstalling twice after but always the same problem. I was able to flash my previous backup no problem, so no damage, but no joy either. Any ideas?
Applejackson said:
Just an update, I tried with my current configuration as I said I would above. Factory Reset, Data Format, the whole nine yards, and everything seems to go smoothly until the final reboot after everything is installed. The phone just hangs on the Samsung boot image and never goes any further. Tried reinstalling twice after but always the same problem. I was able to flash my previous backup no problem, so no damage, but no joy either. Any ideas?
Click to expand...
Click to collapse
I guess I would start with reinstalling the MJ9 firmware through odin, and then try the rom again. You mentioned you were actually on MJB earlier which doesn't sound right.
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.