Related
Hey guys, nice section you have here. I've been reading all about the Atrix and have a couple of questions to confirm what i'm assuming.
Oh yeah, is the Atrix and Atrix 4G the same? I'm assuming so as i've not seen different specs or sections for it here, just wanted to be 100000% sure as i've never owned an android phone!
If i keep the Bootloader locked, is it impossible for me to hard brick the device? Seeing as though i can't freely flash to a lower firmware? (not including things like upgrading to official firmware and running out of battery etc, that's a sure fire way of bricking
Click to expand...
Click to collapse
Just say i'm on 2.3.4 and i'm rooted and unlocked, if i flash CM7, can i reflash something like Alien or MIUI (when or if it gets ported) without ANY chance of a hard brick (AKA does it touch the bootloader and/or does it carry the risks which the flashing of a lower firmware does?)
Click to expand...
Click to collapse
Would LauncherPro and other theme programs be available across the wide range of ROMS as long as i'm rooted?
Click to expand...
Click to collapse
Thanks for your time guys, i'm busy reading up and watching the few videos on youtube (seriously, hardly anyone makes videos about this phone, what's up with that? ) I do have a cold right about now so will take a rest but i can't sleep knowing that i may soon be getting this phone (if my order for a Samsung Galaxy S (1) is not accepted by Vodafone and their stringent credit checks!)
Thanks again guys, hope to see you around soon!
The phone will be on T-Mobile in the UK. Hopefully!
First and last bump! I was wondering if installing LauncherPro would have any negative effects on the speed of the phone? It's dual core and has 1gb ram so i'm thinking the new launcher would not cause any lag but has anyone tried this and found out that it does indeed lag?
No not impossible, i would think it would be easier to brick with a locked bl.
Yes you can reflash, and no you won't get the "lower fw brick".
Yes you can use other launchers, always.
Thanks a lot mate.
To expand on the 1st answer, is it because with the locked BL, i can't install CWM so technically if i brick, it'll be harder if not impossible to fix it? So in a way, an unlocked BL is safer then, as long as i don't try to downgrade? That sounds kinda awesome!
Also, after the first flash, is it easier to flash another rom or is it the same process? I mean, is the 1st flash always the hardest and longest? Because i'm thinking that the 1st time flash would have me install a lot of things, and the next time i reflash, i can use the things i already installed the 1st time (such as CWM etc) to flash another rom can't i? I just want to be able to swap between a few different ROMS without having to risk a hard brick! Thanks for your answers btw, really appreciate it
coolnow said:
Thanks a lot mate.
To expand on the 1st answer, is it because with the locked BL, i can't install CWM so technically if i brick, it'll be harder if not impossible to fix it? So in a way, an unlocked BL is safer then, as long as i don't try to downgrade? That sounds kinda awesome!
Also, after the first flash, is it easier to flash another rom or is it the same process? I mean, is the 1st flash always the hardest and longest? Because i'm thinking that the 1st time flash would have me install a lot of things, and the next time i reflash, i can use the things i already installed the 1st time (such as CWM etc) to flash another rom can't i? I just want to be able to swap between a few different ROMS without having to risk a hard brick! Thanks for your answers btw, really appreciate it
Click to expand...
Click to collapse
Thats right, the unlocked bootloader is the best way to go if you plan on flashing because of custom recovery.
Yes most likely its about the same process BUT, most if not all ROMs will have instructions on how to flash - make sure you read and follow them dont just "do what you did last time".
Prob the easiest way to swap between ROMs easily is to keep nandroid backups for them through cwm.
As far as it being easier to flash the next ROM because you can "keep things from the last flash".. NO you dont want to keep anything between flashing, meaning you should most likley always wipe data, cache & such unless otherwise specified (sometimes upgrading ROMs from one version to the next you can use a "no wipe" upgrade).
Thanks so much! Will install Nandroid asap when i get it! Also, i didn't mean "keep" things as in data and/or apps or cache or whatever, i meant like the 1st flashing would include installing CWM recovery, but the next time i reflash, i won't have to install that again, or would i? If not, then that's great!
Can't wait to try out Cyanogen Mod, theme it up, install some cool apps and just mess around with it! Bookmarked every section of the Atrix forum so i can easily read through it
Thank you for your time in helping a confused noob out I have read a lot of guides but without the phone in front of me, and me being completely new to this, it's not really sinking in. Once i get the phone physically in my hands, then i bet i'll learn a lot more!
coolnow said:
Thanks so much! Will install Nandroid asap when i get it! Also, i didn't mean "keep" things as in data and/or apps or cache or whatever, i meant like the 1st flashing would include installing CWM recovery, but the next time i reflash, i won't have to install that again, or would i? If not, then that's great!
Can't wait to try out Cyanogen Mod, theme it up, install some cool apps and just mess around with it! Bookmarked every section of the Atrix forum so i can easily read through it
Thank you for your time in helping a confused noob out I have read a lot of guides but without the phone in front of me, and me being completely new to this, it's not really sinking in. Once i get the phone physically in my hands, then i bet i'll learn a lot more!
Click to expand...
Click to collapse
Nandroid backup is a backup through CWM, it is not a seperate app. As far as having to install CWM each time.. No you wont have to, the recovery stays but it should be updated when available, unless stated otherwise. Rom Manager will install the latest version of CWM for you. Doing a backup in CWM is known as a Nandroid backup.
Right, i get it now, i was confusing it with Titanium Backup but i've looked at vids about it and know what it does now. Isn't it risky to read/write from NAND a lot? Hmm
Also, if i Nand backed up my stock firmware (before i flash anything), can i restore from there and return to that stock backup anytime i want? If that's possible then i'm sorted!
coolnow said:
Right, i get it now, i was confusing it with Titanium Backup but i've looked at vids about it and know what it does now. Isn't it risky to read/write from NAND a lot? Hmm
Also, if i Nand backed up my stock firmware (before i flash anything), can i restore from there and return to that stock backup anytime i want? If that's possible then i'm sorted!
Click to expand...
Click to collapse
I dont know of any risks to Nandroid backup, only benefits. I have returned to a Nandroid backup on my Captivate but not on the Atrix, i have created a Nandroid backup on (stock) Atrix and recommend do the same jic. I believe you can return to that stock back up (after flashing) if needed but first check out the section on fruitcakes, there is more info along these lines in that thread.
Reading the section now, makes little sense yet but i'm sure i'll understand. What they basically are are roms that don't touch the BL, so doesn't matter if its a lower firmware than the one i'm on because these fruitcakes don't look at the BL and will flash the firmware without bricking, whereas if i downgraded with a stock firmware or something, they touch the BL and will find out it's unlocked and on a newer firmware so the flashing ends up physically bricking the device. That's what i'm basically assuming. Also, read another thread where the OP said he recovered from a stock nandroid backup from a CM7 rom, which sounds a hell of a lot easier than downgrading carefully using special roms!
coolnow said:
Reading the section now, makes little sense yet but i'm sure i'll understand. What they basically are are roms that don't touch the BL, so doesn't matter if its a lower firmware than the one i'm on because these fruitcakes don't look at the BL and will flash the firmware without bricking, whereas if i downgraded with a stock firmware or something, they touch the BL and will find out it's unlocked and on a newer firmware so the flashing ends up physically bricking the device. That's what i'm basically assuming. Also, read another thread where the OP said he recovered from a stock nandroid backup from a CM7 rom, which sounds a hell of a lot easier than downgrading carefully using special roms!
Click to expand...
Click to collapse
Dont worry it makes more and more sense as you learn and play with it. Your assumption of fruitcakes is my understanding as well. I agree that nandroid backup/restore seams a slightly easier method than fruitcakes, but thought I would include the fruitcake methods for you seeing as how you were concerned of a risk with nand, plus the more reading the better. Also NandBacks do take up a good amount of storage space, but are worth it jic. As long as you read you should be just fine, reading here on xda is the best thing you can do to keep from screwing something up. Good luck.
Thank you mate, i really appreciate your time! If i wasn't so ill, i'd be understanding more i think, but i have to look away every few seconds or else my eyes will explode haha, i guess i'm not getting the Galaxy S anymore, i hope i don't regret it! And with the method of hiding the unlocked bootloader, i'm hoping IF anything bad happens, then i still have a chance of tricking the tricksters who gave us these locked down phones in the first place! Android was supposed to be free and open I'm just glad at the thought of getting rid of my iPhone 3g + iTunes + Quicktime.
Also, in your opinion, is ADW EX better than Launcher Pro?
Hi guys,
I've had an S2 for a few months now, and although I've managed to root the phone I'm still pretty green and need help.
I've had an OTA update from Gingerbread to ICS which I only installed as it popped up when I was using the phone.
The battery died earlier than expected and now it's stuck in a bootloop.
I don't want to have to ROM it as frankly I'm still in the "full theory" stage. I've heard of Odin and SamMobile.com, I've seen hours of vids on Youtube but I'm hoping there's another way to get around it. My confidence levels are improving but not there yet.
I have a Titanium backup on the phone from 2.3.4, if I wipe the phone from recovery will it work? Is there anything I can do apart from a new ROM?
If you had my lack of experience with this, what would you do? Thanks.
Can you get into download mode?
If so, you may have to bite the bullet and use Odin to flash the original firmware. You will be able to find it on these forums.
Don't sweat it, just download the Orange ICS ROM and put it in PDA on Odin and flash it, it'll take just a couple of minutes and you are done.
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
FourQ said:
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
Click to expand...
Click to collapse
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Warren.D said:
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nothing confusing about rooting either.
Download one of chainfires cfroot kernels or siyah kernel and flash via Odin.
That's it you're rooted.
----------------------
GTI9100
Hydra H2O 1.2.1
fluxi xx.01_rc5
if ya have a look around the forum, theres plenty of pre-rooted roms to flash via odin that wont increase ya binary counter, nothing hard about that.
Read the links in my signature
Sent from my GT-I9100 using XDA
I'm still reletively new to it
and I've had a couple of bootloops. A bit of a panic and then I figured out what I'd done wrong. As long as you follow instructions to the letter you'll be fine.
Edit: *Relatively, damn it.
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
FourQ said:
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
Click to expand...
Click to collapse
getting a custom rom isn't something you should be afraid of
getting a custom rom (or kernel) can improve your battery life (some of them).. but just be sure that getting a custom rom, it should be for whatever you're running (Gingerbread or ICS) usually, roms are flashable via CWM
take a leap, when you get into bootloop or get some problems along the process, just flash a stock firmware with odin..
@saywhatt
A mate (who's been doing this for years) has installed CWM7. It's odd how the things I liked about Gingerbread were added by Samsung, not Google.
I suspect I'll run with CWM7 for a week or so and decide then. First impressions aren't always correct (especially if you saw my face!) but after a week I should have a pretty good impression of the new ROM. I'm hesitant about ICS as the official version killed the phone but ultimately I may end up there.
It's good to watch the Youtube vids on how to flash stock ROMs with Odin. It's something I may try next week if CWM7 falls from favour.
Ultimately I'm sort of glad it happened. It's given me new confidence to try these things as I know there's a good chance it can all be recovered.
Q
I've never been too afraid of rooting or flashing. My first android device was a cheap piece of rubbish (an LG GTsomething i think), so I built up confidence in rooting and flashing because I didn't care if i damaged my phone.
I would recommend anyone who's not too confident to go out and get a cheap phone, it's a pretty significant investment but if your unsure about what your doing and just want to experiment, it's definitely worth the peace of mind.
...
I'm hesitant about ICS as the official version killed the phone
Click to expand...
Click to collapse
no m8 it didn't, your battery dying while you were updating killed your phone
It had finished a while before that. I was selecting a new font when it died.
You can't stuff up your phone anymore - its already in bootloop, what do you have to lose?
Odin is indeed very easy. Just make sure F.Partition is unchecked. Put the ROM in PDA and flash! Of course, after your phone has been put into download mode and connected to pc via usb and one of the Odin blocks have turned yellow.
Your phone is already rooted? If you made a backup in CWM (NOT Titanium Backup, this won't help you right now, as it's only for apps) you should restore that in CWM. A wipe and factory reset wouldn't help you right bow.
I understand you are a bit skeptic of ICS stock ROM right now, but remember you probably got pushed an early version,.the latest versions are very stable! Though Custom ROM's are the way to go eventually. Try the latest stable Cyanogen ROM.
Sent from my GT-I9100 using Tapatalk 2
@FreeStanler
Good point.
The stock ICS ROM was 4.0.3 if memory serves. It wasn't there for long but I was curious to see which version I'd been upgraded to.
I'm planning to see how this CWM7 ROM sits with me. If I can find out which app is causing this: http://t.co/9GfdXmD I'll probably be happy with it. I need to have a good play about with it to give it a fair chance. May end up with ICS/Stock ICS but for now we'll see how it goes.
Why on earth would you use Cm7 when Cm9 is far better, plus to flash a fw & then root with SuperOneClickRoot, or use the cf root kernel. The whole process takes 5 mins. Honestly M8 there's nothing to worry about. One thing I will say tho, Google Nandroid back up & once you know how to use etc, use it & make it your best friend coz that's the only thing that will fix the bootloop in the future
Sent from my GT-I9100 using xda premium
@blade30p
I didn't. A friend who's been doing this for years did it for me. I was hoping to get something resembling the stock Gingerbread on the phone, instead I got CWM7.
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
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Bump in hopes of someone's experience or advice.
falkon114 said:
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Click to expand...
Click to collapse
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
*see below*
Jiggabitties said:
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
Click to expand...
Click to collapse
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
falkon114 said:
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
Click to expand...
Click to collapse
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Jiggabitties said:
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Click to expand...
Click to collapse
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
falkon114 said:
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
Click to expand...
Click to collapse
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Jiggabitties said:
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Click to expand...
Click to collapse
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
falkon114 said:
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
Click to expand...
Click to collapse
Glad I could help in any way. Bummer about your camera.
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.