Related
I'm fairly new to the whole rooting business, and got my phone rooted the first day I had it and customized it how I wanted. Now I want to wipe it to try some new stuff. I've already backed everyone up with Titanium Backup and made a Nandroid recovery, but when I performed a factory reset/data wipe, I reset my phone and it still loaded my rom (the dasBAMF 3.0). Since I wiped but my Rom loaded (my assumption at least) something isn't working correctly and my keyboard won't pop up when I need to type in text for anything. Did I miss a step to completely wipe my phone...?
EDIT***
Really, I just want to try and get my phone either back to stock, or as close as I can (since I don't know what they check for when trying to exchange at the verizon store, if possible) so that my warranty is voided and stuff....
Yeah... You missed the who step of flashing another ROM. It's going revert back to the last ROM that was there if it isn't replaced.
Oh :/ Where would the vanilla TB rom be? Cause I might just be missing it, but I can't seem to find it in Android Development.
I would prefer to exchange it for another phone, so I'm trying to get it back to stock (or as close to it as I can if all they do is look at it without checking so I can exchange).
You're gonna want what's called an RUU. I'm not sure where the most recent OTA RUU is or who's been taking care of those. It should be in the dev forum. The version number should start with 1.70. To flash it, change the name to pg51img.zip and flash it like you would a radio. It will snap your phone right back to factory stock. If you can't find it, let me know and I'll try to hunt it down.
There's this:
http://forum.xda-developers.com/showthread.php?t=997724&highlight=RUU
but none of the file names start with 1.7? Also, the TS has in caps red: "DO NOT FLASH THESE OVER ROOTED DEVICES, UNLESS YOU KNOW WHAT YOU ARE DOING." and I wouldn't know what to do with it even if I got the RUU that started with 1.7.
EDIT***
Well, I found this:
http://forum.xda-developers.com/showthread.php?t=1009423
Since I'm new, that will work for me too, correct? I see nothing stating that it shouldn't...
iImmortality said:
There's this:
http://forum.xda-developers.com/showthread.php?t=997724&highlight=RUU
but none of the file names start with 1.7? Also, the TS has in caps red: "DO NOT FLASH THESE OVER ROOTED DEVICES, UNLESS YOU KNOW WHAT YOU ARE DOING." and I wouldn't know what to do with it even if I got the RUU that started with 1.7.
EDIT***
Well, I found this:
http://forum.xda-developers.com/showthread.php?t=1009423
Since I'm new, that will work for me too, correct? I see nothing stating that it shouldn't...
Click to expand...
Click to collapse
That last link, got to restore to stock for root and non-root users... That will work. Basically, after you flash the first one you'll be stock without root. The second flash will restore S-on.
Ok, so I readily admit that I'm the jackass the n00b video was aimed at. I thought I understood what I was doing, and clearly didn't. Now I can't get my phone to do ****.
I was attempting to flash the new CM9 beta. First time I've attempted to flash anything.
was on 2.3.5.
rooted using the 2.3.5 root method.
SBF-ed to 2.3.4. (prob didn't need to root on 2.3.5 if I was going to sbf to 2.3.4, but I'm an idiot)
SBF went fine. then I messed up good.
at the end of Moon Shadow's SBF tutorial he said he recommends the full factory reset, so I did it.
so now...I have no phone service. looking at settings/about phone it doesn't know my phone # and I have no idea how to fix this. not sure what other problems will present themselves after that, but that's the big issue. I'm connected to my home network, so at least I have some data connectivity.
before starting...
I made a backup with Clockwork Recovery, but that backup seems to be gone.
I made a backup with Go Backup, and that seems to still be there, but it was a 2.3.5 backup...how can I get to that and will it fix my problem?
ideally right now I'd just like to go back to the Go Backup backup I made before starting any of this and then I can reconsider where to go next.
additionally, I thought about just going forward, but I cannot for the life of my figure out how to flash this CM9 ROM, despite having read the directions 15 times. I tried to use Clockwork to install it from SD, but when I try that I can't see the .zip, despite having copied it over.
Can anyone take pity on a n00blet, or point me to a thread with information on how to solve this (I searched and had trouble finding anything useful)?
Very appreciative of all help.
Croda said:
Ok, so I readily admit that I'm the jackass the n00b video was aimed at. I thought I understood what I was doing, and clearly didn't. Now I can't get my phone to do ****.
I was attempting to flash the new CM9 beta. First time I've attempted to flash anything.
was on 2.3.5.
rooted using the 2.3.5 root method.
SBF-ed to 2.3.4. (prob didn't need to root on 2.3.5 if I was going to sbf to 2.3.4, but I'm an idiot)
SBF went fine. then I messed up good.
at the end of Moon Shadow's SBF tutorial he said he recommends the full factory reset, so I did it.
so now...I have no phone service. looking at settings/about phone it doesn't know my phone # and I have no idea how to fix this. not sure what other problems will present themselves after that, but that's the big issue. I'm connected to my home network, so at least I have some data connectivity.
before starting...
I made a backup with Clockwork Recovery, but that backup seems to be gone.
I made a backup with Go Backup, and that seems to still be there, but it was a 2.3.5 backup...how can I get to that and will it fix my problem?
ideally right now I'd just like to go back to the Go Backup backup I made before starting any of this and then I can reconsider where to go next.
additionally, I thought about just going forward, but I cannot for the life of my figure out how to flash this CM9 ROM, despite having read the directions 15 times. I tried to use Clockwork to install it from SD, but when I try that I can't see the .zip, despite having copied it over.
Can anyone take pity on a n00blet, or point me to a thread with information on how to solve this (I searched and had trouble finding anything useful)?
Very appreciative of all help.
Click to expand...
Click to collapse
ok, noob found thread about activation and fixed that part.
now I'm hoping I can just go back to 2.3.5 and apply my backup.
Lol, first take a deep breath. Your phone is not hosed, it's actually working like it's supposed too.
After you sbf, you phone is back to it's factory state right? So remember when you got your phone for the first time you had to have it activated/programmed. If you're on Verizon then dial *228 and follow the directions, takes about 5 minutes. This will give you back service and your phone number.
Second, the droid x2 is unique and requires a few different steps than most phones to flash things because it has whats called a locked, encrypted bootloader. So with the X2 you will NEVER want to use Rom Manager (Clockwork Mod Recovery) or Rom Toolbox. They just do not work with our phone yet.
Your going to want to read this link: http://www.droidxforums.com/forum/droid-x2-support/41785-common-x2-questions-answers.html
It gives a good overview of how the X2 works and explains a lot of things.
Then go here: http://forum.xda-developers.com/showthread.php?t=1318083
This explains how to install and get into the X2's special Bootstrap Recovery. This is where you will make backups, restore backups, and flash new roms. The thread explains in great detail how to make and restore backups in Bootstrap Recovery.
oh man, thanks a bunch lead off.
that whole deal with the boot strap is something that I never saw in all the reading I did and probably solves a lot of my problems. I'll do what you said (starting with the deep breath) and begin again.
thanks again for the help.
Yea no problem
I've been trying to understand all the steps necessary to replace the OEM ROM in my HTC Amaze 4G phone, but I can only find a disjointed set of pieces about the various steps and not one overarching document that covers all the stages of custom ROM flashing. A lot of the docs are aimed at the "insiders" of the Android developer community and few to people like me who would just like to try something better than what that ICS update did to my phone.
Having dabbled at one time with Linux from version .98 to 2.6 and being software developer most of my working life, I figure this should be easy for me. Yet, I find the documentation frustrating. I only imagine what it must be for others with less computer experience than me.
Since Android is based on Linux, I don't understand the big fuss about rooting. In Linux having the rooting privilege simply meant having a root password. Why is Android so much more complicated than that? Also, loading a new Linux kernel used to be a fairly simple process if one used compiled modules. The installation script pretty much took care of it. Android totally obscures this process and the disjointed documentation doesn't seem to help much. A lot of it assumes certain knowledge by the reader as if he/she was also an "insider" in that circle.
On my part I would like to so the following steps documented:
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
2.) How to prepare the phone for installing a new ROM
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
5.) How the flashing process would look like? Expected phases and length?
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
7.) Any special issues when booting the new ROM for the first time?
8.) How would I restore the original factory ROM saved in step 1?
Some of you might think I ask too much from guys who do the dev work as a hobby but I always thought that if one does something, might as well do it right, regardless of pay.
Well, that's my 2 cents worth for the day.
Howdy. I'll try to answer some of the questions you asked.
I would also recommend talking with @ravike14 who can easily guide you through the back up and routing and s-off process. It's not that difficult really. The most bizarre thing for me was sticking a piece of wire into a hole in the back of the phone to short out a process to achieve s-off.
With the right recovery image installed, it won't matter where you place the Rom.zip. which may be named just about anything. But it will always be a zip file.
The important one is the PH85img.zip must be placed in the root of your external sdcard. That file is loaded when you boot into the bootloader. And is for updating firmware.
Once you have root, and have made a nandroid backup, flashing is easy.
If you download viper, it is vipera1.7.2.1.zip. you can have it anywhere on you internal or external sdcard.
If you use 4ext recovery, you can select install and it will take you to a directory that you can browse to the place where the Rom, whatever name it is, is stored.
Click the Rom zip file and you will be guided thru the install process, if it has an aroma installer, or it will just install otherwise.
Then reboot and go thru the set up as if it was a brand new phone.
If you don't do the s-off thing, 4ext offers a smart flash option. If you aren't s-off you can't just flash a Rom if it contains a kernel. So smart flash will be required.
There are a few guides in the dev section and the general section on how most of this process works.
Again, talk with ravike and he'll be glad to help. Plus the more people we can keep here and happy, the longer we will be creating roms and fun stuff to play with.
Regards,
Chevy
Sent from my HTC_Amaze_4G using xda app-developers app
Is there a good documentation for all ROM flash steps?
Thanks, Cowboy, for the helpful reply, though I don't see any HELP button to push that the end of your post refers to.
I think at this point I'd like to figure out on my own how to install a custom ROM, though I must say that your S-OFF reference is one of the things that confuses me because the HTC dev site itself spells out that it is not necessary to change S-On to S-Off. Go, figure ...
Also, I think I like what I've read about the Revolution ROM, so that's the one I'd like to install if that is working with T-Mo branded Amaze 4G phones, though mine is no longer locked to T-Mo.
Your welcome!
NWsoccerfan said:
Thanks, Cowboy, for the helpful reply, though I don't see any HELP button to push that the end of your post refers to.
I think at this point I'd like to figure out on my own how to install a custom ROM, though I must say that your S-OFF reference is one of the things that confuses me because the HTC dev site itself spells out that it is not necessary to change S-On to S-Off. Go, figure ...
Also, I think I like what I've read about the Revolution ROM, so that's the one I'd like to install if that is working with T-Mo branded Amaze 4G phones, though mine is no longer locked to T-Mo.
Click to expand...
Click to collapse
If you're using the web to look at xda, there is a thanks button on the lower left side of the screen before the very end of the post line.
If you're using the XDA app, you have to tap on my post, and it should have a thanks selection in the options that come up.
A few more suggestions.
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
A) one you are rooted you should be able to back up all of your user data through a nandroid which is available in TWRP or 4EXT recoveries. This will back up everything to be able to restore exactly like it was before you change roms.
(NRG is my ICS preference, and Afnan has a good modified stock rom. ARHD (revolution) is also a good one without too many frills.
2.) How to prepare the phone for installing a new ROM
B) again, Root - s-off (really a good idea and not too hard to do) - dev unlock - and Super CID
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
C) any roms listed in the dev section in the Amaze forum works. And, they should all be Zip fles. You can restore somone elses nandroid back up, but not adviseable.
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
D) anywhere (except the PH85IMG.zip MUST be on the root of your EXTERNAL sdcard)
5.) How the flashing process would look like? Expected phases and length?
E) There are two types of rom flashes, standard and Aroma (thanks @amarullz)
1) Standard just does it's thing and when it's done, it returns you to the recovery menu to reboot.
2) Aroma is a highly configurable installation (preferred for selections of different kernels and adding or removing apps, keyboards, cpu freq's and much more) after it's done, most often it can reboot directly from the installer. ARHD has this type of installer, also NRG roms, and mine!
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
F) all of the "Custom" rom's (even thought some may be stock) should be rooted. A rooted rom containd the busybox and super user bianaries and apps (IE chanfireSU or SuperSU)
7.) Any special issues when booting the new ROM for the first time?
G) You shouldn't have any issues when booting a new rom for the first time. Some do require a little bit of behind the scenes set up time. Most users see just the boot animation reach the end, or it may seem like it's not doing anything, but it's doing an unbelievable amount of background processing, dexopting, and some comminucation with the carrier for data and validation set up. Some may take five to ten minutes to complete depending on the amount of apps and goodies that are in the rom.
H) if you see the HTC logo for an extended amount of time, more than five minutes, and you dont see the boot animation (which varies by rom) then you are stuck in a preload loop. This happens when you flash a carrier specific rom without being "Super CID", or you may not have flashed the kernel (if you are S-Off this won't be a problem) because you didn't select smartflash from the recovery settings.
** I had issues trying to install ARHD at first because there is a firmware update, a requirement to be Super CID (probably the easiest of things to do), and some roms specify that you should be using TWRP recovery instead of 4EXT, or vise versa.
8.) How would I restore the original factory ROM saved in step 1?
I) nandroid restore There is also a rooted stock rom based off of the latest OTA ICS Update. It is just like the rom that comes preloaded, or updated to on stock non-rooted phones. If you go that route, flash the "Stock ICS" rooted rom and do an advanced nandroid restore and only restore your data. That will (should) get you back to where you started from but keeping root, S-Off, Dev unlock, and Super CID.
I rewrote some of what I noted befor so maybe other's can benifit from this knowledge. And I wanted to expand on a few items. All good questions!
There's a lot of things that happen in the background that people need to see sometime (pull a logcat) to see the crazy lines of code flying by on a terminal screen.
If more poeple took the time to understand all of this it would reduce the amount of errors while flashing and poeple would be more happy.
And in doing so I think people will learn more about what they are doing, and the more you do it, the better you get at doing it.
Enjoy!
Chevy
chevycowboyusa said:
If you're using the web to look at xda, there is a thanks button on the lower left side of the screen before the very end of the post line.
If you're using the XDA app, you have to tap on my post, and it should have a thanks selection in the options that come up.
Click to expand...
Click to collapse
I use the web for this and the only thing I see on the lower left side is a DONATE button. That's what you mean?
chevycowboyusa said:
A few more suggestions.
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
A) one you are rooted you should be able to back up all of your user data through a nandroid which is available in TWRP or 4EXT recoveries. This will back up everything to be able to restore exactly like it was before you change roms.
(NRG is my ICS preference, and Afnan has a good modified stock rom. ARHD (revolution) is also a good one without too many frills.
2.) How to prepare the phone for installing a new ROM
B) again, Root - s-off (really a good idea and not too hard to do) - dev unlock - and Super CID
Click to expand...
Click to collapse
Can I still use my phone after it is rooted but before the new ROM is installed? How would the phone behavior change on a rooted phone?
You did not comment on why the htcdev site recommends against the S-Off as not being necessary for installing a custom ROM.
chevycowboyusa said:
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
C) any roms listed in the dev section in the Amaze forum works. And, they should all be Zip fles. You can restore somone elses nandroid back up, but not adviseable.
Click to expand...
Click to collapse
OK, I've got that. Does this Nandroid backup the entire image of the phone's content sector-by-sector, or as individual files? To the external SD card or to the PC connected by USB cable? BTW, why are all flashing procedures requiring loading of the HTC USB drivers when such drivers must be on the phone already? Otherwise we could not link the phone to PC in the first place.
chevycowboyusa said:
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
D) anywhere (except the PH85IMG.zip MUST be on the root of your EXTERNAL sdcard)
5.) How the flashing process would look like? Expected phases and length?
E) There are two types of rom flashes, standard and Aroma (thanks @amarullz)
1) Standard just does it's thing and when it's done, it returns you to the recovery menu to reboot.
2) Aroma is a highly configurable installation (preferred for selections of different kernels and adding or removing apps, keyboards, cpu freq's and much more) after it's done, most often it can reboot directly from the installer. ARHD has this type of installer, also NRG roms, and mine!
Click to expand...
Click to collapse
Aroma? That doesn't smell too good to me.
chevycowboyusa said:
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
F) all of the "Custom" rom's (even thought some may be stock) should be rooted. A rooted rom containd the busybox and super user bianaries and apps (IE chanfireSU or SuperSU)
Click to expand...
Click to collapse
Oh, so this might answer my earlier question about how a rooted phone might behave. Essentially a user might not even know the difference, right? So, I could also do this process in two stages: First just root the factory ROM and use the phone that way till I am ready to actually flash the new ROM in the second stage, right?
chevycowboyusa said:
7.) Any special issues when booting the new ROM for the first time?
G) You shouldn't have any issues when booting a new rom for the first time. Some do require a little bit of behind the scenes set up time. Most users see just the boot animation reach the end, or it may seem like it's not doing anything, but it's doing an unbelievable amount of background processing, dexopting, and some comminucation with the carrier for data and validation set up. Some may take five to ten minutes to complete depending on the amount of apps and goodies that are in the rom.
H) if you see the HTC logo for an extended amount of time, more than five minutes, and you dont see the boot animation (which varies by rom) then you are stuck in a preload loop. This happens when you flash a carrier specific rom without being "Super CID", or you may not have flashed the kernel (if you are S-Off this won't be a problem) because you didn't select smartflash from the recovery settings.
** I had issues trying to install ARHD at first because there is a firmware update, a requirement to be Super CID (probably the easiest of things to do), and some roms specify that you should be using TWRP recovery instead of 4EXT, or vise versa.
Click to expand...
Click to collapse
I've got this.
chevycowboyusa said:
8.) How would I restore the original factory ROM saved in step 1?
I) nandroid restore There is also a rooted stock rom based off of the latest OTA ICS Update. It is just like the rom that comes preloaded, or updated to on stock non-rooted phones. If you go that route, flash the "Stock ICS" rooted rom and do an advanced nandroid restore and only restore your data. That will (should) get you back to where you started from but keeping root, S-Off, Dev unlock, and Super CID.
I rewrote some of what I noted befor so maybe other's can benifit from this knowledge. And I wanted to expand on a few items. All good questions!
There's a lot of things that happen in the background that people need to see sometime (pull a logcat) to see the crazy lines of code flying by on a terminal screen.
If more poeple took the time to understand all of this it would reduce the amount of errors while flashing and poeple would be more happy.
And in doing so I think people will learn more about what they are doing, and the more you do it, the better you get at doing it.
Enjoy!
Chevy
Click to expand...
Click to collapse
Thanks. I like your attitude about this.
When you get time stop by
XDA University.
I learned tons here its a great place to start and much better than trying to Google everything
http://forum.xda-developers.com/general/xda-university
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
been busy
NWsoccerfan said:
I use the web for this and the only thing I see on the lower left side is a DONATE button. That's what you mean?
Can I still use my phone after it is rooted but before the new ROM is installed? How would the phone behavior change on a rooted phone?
You did not comment on why the htcdev site recommends against the S-Off as not being necessary for installing a custom ROM.
OK, I've got that. Does this Nandroid backup the entire image of the phone's content sector-by-sector, or as individual files? To the external SD card or to the PC connected by USB cable? BTW, why are all flashing procedures requiring loading of the HTC USB drivers when such drivers must be on the phone already? Otherwise we could not link the phone to PC in the first place.
Aroma? That doesn't smell too good to me.
Oh, so this might answer my earlier question about how a rooted phone might behave. Essentially a user might not even know the difference, right? So, I could also do this process in two stages: First just root the factory ROM and use the phone that way till I am ready to actually flash the new ROM in the second stage, right?
I've got this.
Thanks. I like your attitude about this.
Click to expand...
Click to collapse
you're welcome! I wish everyone would try to learn this
and the university is also very helpfull as freakboy noted above,
I've been busy working at bringing the comunity the next greatest romz!
I'm gonna go out on a limb here & ask a question that's been on my mind for a while, so bear with me. But first, let me give you some background so there's no confusion & no unnecessary questions asked. I'm by no means a "pro" at modifying my Note 3, I just follow instructions carefully & then implement those directions to achieve results. That's how I rooted my Note 3 but could still care less that I tripped Knox in the end.
I have the 32 GB Sprint Galaxy Note 3 with an 8 GB microSD. It's rooted using Chainfire's method. I also have TWRP for a recovery, but I'm using the stock Sprint ROM that came with it. I have a few root apps installed (Titanium backup, AdAway & Root Explorer) but the rest are what Sprint (& Android) put in there, minus a few that are totally unnecessary for me...(chat apps, picture drawings, step counting & so on) that were removed with Titanuim. It's still on 4.3 Jellybean with PUBMJ4 baseband. I also have the Wi-Fi hotspot fixed through 2 file replacements using Root Explorer.
Now that you know what I have, onto the question...
I see many, many ROMs in other threads that I'd like to try out, but don't know how to go about doing this. Before you jump right in & answer, here's my problem. If I try a ROM but don't like it, or it doesn't suit my needs, how can I go about going back to what I have now in the best (& fewest) steps necessary? In other words, to go back to exactly what ROM I have now, the apps installed, baseband, the whole nine yards. Just like a computer backup, it's a bit-for-bit restore, completely mirroring the hard drive. Understand?
Maybe you could explain to me like I'm seven years old what apps I need, what procedures are taken, the order in which they happen & so on. If I need an app or two to do just this, I have approximately $20 Google Play credit left.
Can a DEV or an experienced person that's done just this help a fellow out? Don't get me wrong, the stock ROM I'm using works for me, but there's ROMs posted that look just awesome! It's all about "personalization", am I right?
Easy, since you have a custom recovery installed (twrp) , you simply do a "nandroid" backup (I personally like to backup to an external SD card, so get a bigger one) before wiping and installing something new. If you like what you got, fine. If you want to go back, wipe and restore! Easy Peasy!
Sorry, being a father means sometimes your time suddenly becomes unavailable. But believe me, it's really easy once you figure out twrp.
I'll let another fine member get more details if you actually need them. ?
Sent from my calculator watch.
So did you figure it all out?
Sent from my SM-N900P using Tapatalk
kingdazy said:
Easy, since you have a custom recovery installed (twrp) , you simply do a "nandroid" backup (I personally like to backup to an external SD card, so get a bigger one) before wiping and installing something new. If you like what you got, fine. If you want to go back, wipe and restore! Easy Peasy!
Sorry, being a father means sometimes your time suddenly becomes unavailable. But believe me, it's really easy once you figure out twrp.
I'll let another fine member get more details if you actually need them. ?
Sent from my calculator watch.
Click to expand...
Click to collapse
Doing a Nandroid backup as we speak! I didn't realize TWRP could do that. (duh! ) I only installed TWRP because I just liked the name of it. TWERP!! (gotta nice sound to it, doesn't it??) Thanks a bunch! :good:
tonyevo52 said:
So did you figure it all out?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I did. I found a Youtube link on how to do a TWRP backup on the Sprint Note 3. Easy Peasy as said above! I'll try some ROMs this weekend (can't promise nuthin' cause it's gonna be 70 degrees this weekend & I'm itchin' to ride my mountainbike along the boardwalk at the Virginia Beach.)
But now that the hard part is outta the way, it's all easy street from here!
Just be sure to Please, oh god Please, read all instructions on any rom you decide to try. Doesn't hurt to read the last 10 pages of each too, get an idea of Current issues that may not be documented in the OP.
And don't get lazy, follow word for word. The only times I f*cked stuff up was when I didn't follow instructions (ie, thought my experience meant I knew best), or just got sloppy.
And, don't forget to wipe! (I wipe 3X, everytime, as a habit. Some people will give you reasons why that's unnecessary, but I can say confidently, if perhaps anecdotally, that I Never have the issues others have with bad flashes, softbricks, FCs, etc.)
Something to get comfortable with, even though you may never need it is ODIN. It's most common use is a utility for flashing stock ROMs and firmwares, great for recovery from bad things. Again, you may never need it, but have it ready in your Pc with a stock ROM file, just in case.
Finally, Titantium Backup can be your best friend, if used properly. It can also be a real pain, so don't become too dependant on it.
FIN
Sent from my calculator watch.
kingdazy said:
Just be sure to Please, oh god Please, read all instructions on any rom you decide to try. Doesn't hurt to read the last 10 pages of each too, get an idea of Current issues that may not be documented in the OP.
And don't get lazy, follow word for word. The only times I f*cked stuff up was when I didn't follow instructions (ie, thought my experience meant I knew best), or just got sloppy.
And, don't forget to wipe! (I wipe 3X, everytime, as a habit. Some people will give you reasons why that's unnecessary, but I can say confidently, if perhaps anecdotally, that I Never have the issues others have with bad flashes, softbricks, FCs, etc.)
Something to get comfortable with, even though you may never need it is ODIN. It's most common use is a utility for flashing stock ROMs and firmwares, great for recovery from bad things. Again, you may never need it, but have it ready in your Pc with a stock ROM file, just in case.
Finally, Titantium Backup can be your best friend, if used properly. It can also be a real pain, so don't become too dependant on it.
FIN
Sent from my calculator watch.
Click to expand...
Click to collapse
No worries! As I said in the OP, I follow directions carefully. I read everything.
Odin is my friend as well. I have it installed on my laptop. That's how I flashed basebands & deodexed stock rooted ROMs on my Galaxy S III. I also have the original stock Sprint ROM for this GN3 "just in case", in a folder sitting on my desktop with a few extra tools. I've never bricked a phone, unless you count using Samsung's online update (can't think of the name at the moment). It said 4.3 was available, so I downloaded it. It flashed, rebooted, but stuck there. Never finished the boot, just gave me an error code. Samsung's own update killed my GS3 & was unrecoverable. Believe me, I tried everything. What was strange, was the ROM was 4.3 but the baseband was the previous version, not the newer one, so the phone just puked. It never updated the baseband so it bricked. Now, I tried (and used) different radios with no problems before the update. Everything worked in harmony. Go figure!
Time for sleep my friend. Gotta work in the morning!
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.