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!
Related
So I'm pretty sure I'm going to flash that new rom once I'm home but i haven't done one of those nandroid back ups since the infuse was new...can someone point me in the right direction, i forgot how to do it. Do i really need to do it?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
u can just boot recovery and then go to backup n restore and select backup no?
Sent from my SAMSUNG-SGH-I717 using XDA
You need to flash clockwork recovery then just go to the backups menu and do a backup. If you're going to install the Solaris rom you need clockwork anyway.
And DONT SKIP THE BACKUP!! I cannot stress this enough!
sent from my iPhone killers killer, Samsung Galaxy Note.
Backup up, backup always
Sent from the only smartphone designed by Chuck Norris
macked said:
You need to flash clockwork recovery then just go to the backups menu and do a backup. If you're going to install the Solaris rom you need clockwork anyway.
And DONT SKIP THE BACKUP!! I cannot stress this enough!
sent from my iPhone killers killer, Samsung Galaxy Note.
Click to expand...
Click to collapse
That's what i plan on doing...thanks.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Always always backup. I am a hypocrite (and many probably are) when I say this as I have skipped the back up. But I have learned the hardway. When I got into flashing with my G1 I soft bricked for about 3 days. This scared the bajesus out of me as there was no wide spread support, this was the first commercialy available android phone so any sites that did exsist were in their infantile stages at the time. I dodged the bullet and found someone who was able to get me fixed, but was a real PITA. The odds of this heppening are far less now a days so long as you read the instructions and follow them, but it's still not worth the risk. Doing a CWM backup takes a few minutes so there is no reason not to do one. Something else I learned the hard way the most people overlook, TEST THE BACKUP. Lucky for me I never got in an instance where my failed backup caused me anything but a little more work. I can think of atleast a half dozen times I created a backup that would fail when I tried to restore to it. If restoring the backup failes, you will be able to just boot back up into your ROM. However if your stuck in a bootloop from a failed ROM flash, and now your backup wont flash, you're in a little hot water. Likely you'll just have to pop your SD, xfer a couple images onto it, then back to phone and start flashing till you get one to boot up. Learn from those who have already been stupid, laughing at us is better then people laughing at you down the road.
Chief Geek said:
Always always backup. I am a hypocrite (and many probably are) when I say this as I have skipped the back up. But I have learned the hardway. When I got into flashing with my G1 I soft bricked for about 3 days. This scared the bajesus out of me as there was no wide spread support, this was the first commercialy available android phone so any sites that did exsist were in their infantile stages at the time. I dodged the bullet and found someone who was able to get me fixed, but was a real PITA. The odds of this heppening are far less now a days so long as you read the instructions and follow them, but it's still not worth the risk. Doing a CWM backup takes a few minutes so there is no reason not to do one. Something else I learned the hard way the most people overlook, TEST THE BACKUP. Lucky for me I never got in an instance where my failed backup caused me anything but a little more work. I can think of atleast a half dozen times I created a backup that would fail when I tried to restore to it. If restoring the backup failes, you will be able to just boot back up into your ROM. However if your stuck in a bootloop from a failed ROM flash, and now your backup wont flash, you're in a little hot water. Likely you'll just have to pop your SD, xfer a couple images onto it, then back to phone and start flashing till you get one to boot up. Learn from those who have already been stupid, laughing at us is better then people laughing at you down the road.
Click to expand...
Click to collapse
Good points but the first time i bricked my phone (flashed a gb rom over my froyo infuse) i just used the ultimate unbrick tool and bam back to stock, yea i have to start over from stock but at least my phone is all set. Is there a tool available for the note that unbricks it like the infuse has or is the back up we make our only option to unbrick?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Do. It. (just do it)
Do it. Back it up!
Sure it adds a few minutes to your flashing routine, but just start it and go make a coffee.
I cannot begin to tell you how many times I was glad to have something to restore to after playing around with a new/updated rom package.
nash2000 said:
Good points but the first time i bricked my phone (flashed a gb rom over my froyo infuse) i just used the ultimate unbrick tool and bam back to stock, yea i have to start over from stock but at least my phone is all set. Is there a tool available for the note that unbricks it like the infuse has or is the back up we make our only option to unbrick?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
Nope, nothing that I know of, but the ROM scene is in its early stages. Theres not much need for tools such as this when there is little action. Something like this may hit the scene once our Note starts getting lots of custom ROM releases. I have only heard of that tool for two phones though. It's pretty hard to truely brick a phone nowadays, if you download the right packages and read the instructions a couple times and then (heres a commonly skipped one) FOLLOW the flashing directions, you won't encounter too many issues that can't be easily overcome by restoring image, delete rom and redownload, and try again. Alot of ICS ROMS actually require a double flash, if you don't read the instructions and don't catch that, you'll be freaking on the boot loop.
nash2000 said:
So I'm pretty sure I'm going to flash that new rom once I'm home but i haven't done one of those nandroid back ups since the infuse was new...can someone point me in the right direction, i forgot how to do it. Do i really need to do it?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
Should always backup before flashing something, just as a precaution.
Although I don't worry too much, it's fun re-customizing anyways. Going into market online and reinstalling apps is quick. Contacts and calender restores from google, at least for me anyways.
If you're thinking of flashing a new radio or going into something that makes major changes to the way your device is configured. I would highly recommend you have a nand of your last working setup. In case you need to revert.
clockcycle said:
Should always backup before flashing something, just as a precaution.
Although I don't worry too much, it's fun re-customizing anyways. Going into market online and reinstalling apps is quick. Contacts and calender restores from google, at least for me anyways.
If you're thinking of flashing a new radio or going into something that makes major changes to the way your device is configured. I would highly recommend you have a nand of your last working setup. In case you need to revert.
Click to expand...
Click to collapse
I think we're more concerned with if the image doesn't flash or he gets stuck in a boot loop. If your able to get to CWM, you can recover. But having something to flash from immediately on hand is a very nice thing to have. As for recustomizing though, i'm with you all the way there. I look at as a good way to cut the fat. I use Titanium backup, but don't do full automated restores, but rather select the desired apps and ignore the rest untill I find myself needing it.
First and foremost. I BIG Thank You to all the Dev's that give us these awesome tools and ROMS!
I probably should have put this in the Gen section, mods move if needed.
I have sent several hours the last 2 days with a goal in mind. That is to update my Amaze 4g to Jelly Bean, and restore my phone as it is now running JB
I feel that the best option will be AIO, and the 4EXT touch panel...be glad to pay and contirbute to this program and dev.
I believe I have a handle on most things now. But to make sure, I reread the tutorials follow videos etc...then this tutorial seems to direct me to another thread, click on that to ensure I'm not going to screw things up...it will be a dead link. So, back to reading other stuff again.
I finally understand recovery after I saw it mentioned many times. SO, according to the AIO, I'll need to flash a recovery. I couldn't find in my search, do I use the 4EXT contol panel, or the 4EXT free file. Is that what AIO needs. Not sure, did more searching. Still not sure.Then after these steps are complete, do I need to update the kernel? Again, not sure.
Then I come to the point of backing up everything. My goal is to have the new ROM running and then restore everything as it is now runnig ICS.
Is that possible? I'm not sure, as my search didn't find too much useful. I see Backup Pro recommended, will this accomplish my "cloning" if you will of my phone after ROM update....not sure.
Then, in regards to S-OFF. I will use the AIO for that as well. But again, not sure when to use it. Do I do that after the rooting, or before. From what I read, S-OFF will wipe your data. But, I understand it will leave the external SD card alone?
Then I get to the actual Jelly Bean ROM. It seems as though the CM10 seems to be the one to use. So, as i read about it's features; I see that the speakerphone volume doesn't work. Little confused, as to if speakerphone is the actual handset or the speakerphone when selected.
If it's the handset, I don't use BT so I would be DOA. Does this pertain to all the JB ROMS? It looked like there were only 2 actual JB Roms.
My other concern not addressed yet. A mention of the service being dropped on TMOUS with CM10.
So, I have tried to find out my info, but even when I do; it seems to take me to another path of more information. Hence further confusion.
This is not really a question per se, just wanted to show how I followed several paths; and still confused .
I know one of my biggest issues, is not using the search but inputting the correct data to get the answer I'm seeking. Which is why, I was all over the place.
I'm sure some reading this post will be Fire,Ready Aim. That's OK...Life's to short. After 2 days of this, I have to ask myself...is it worth it to me to accomplish this? Answer, Yes. So, I'll keep trying, till I have a comfort level of doing everything right the first time.
I guess, even though you have produced some great "Hand holding" tools, tutorials etc; there are still some "dummies"..me, that can still get confused.
I guess it would be like me putting you into the B737 I fly, even though you have a manual that tells you everything, you'll still have questions.
Thanks for allowing me to vent.
b737
PS mods, if you feel this is a waste of space, please delete....and I'll move on.
b737 said:
First and foremost. I BIG Thank You to all the Dev's that give us these awesome tools and ROMS!
I probably should have put this in the Gen section, mods move if needed.
I have sent several hours the last 2 days with a goal in mind. That is to update my Amaze 4g to Jelly Bean, and restore my phone as it is now running JB
I feel that the best option will be AIO, and the 4EXT touch panel...be glad to pay and contirbute to this program and dev.
I believe I have a handle on most things now. But to make sure, I reread the tutorials follow videos etc...then this tutorial seems to direct me to another thread, click on that to ensure I'm not going to screw things up...it will be a dead link. So, back to reading other stuff again.
I finally understand recovery after I saw it mentioned many times. SO, according to the AIO, I'll need to flash a recovery. I couldn't find in my search, do I use the 4EXT contol panel, or the 4EXT free file. Is that what AIO needs. Not sure, did more searching. Still not sure.Then after these steps are complete, do I need to update the kernel? Again, not sure.
Then I come to the point of backing up everything. My goal is to have the new ROM running and then restore everything as it is now runnig ICS.
Is that possible? I'm not sure, as my search didn't find too much useful. I see Backup Pro recommended, will this accomplish my "cloning" if you will of my phone after ROM update....not sure.
Then, in regards to S-OFF. I will use the AIO for that as well. But again, not sure when to use it. Do I do that after the rooting, or before. From what I read, S-OFF will wipe your data. But, I understand it will leave the external SD card alone?
Then I get to the actual Jelly Bean ROM. It seems as though the CM10 seems to be the one to use. So, as i read about it's features; I see that the speakerphone volume doesn't work. Little confused, as to if speakerphone is the actual handset or the speakerphone when selected.
If it's the handset, I don't use BT so I would be DOA. Does this pertain to all the JB ROMS? It looked like there were only 2 actual JB Roms.
My other concern not addressed yet. A mention of the service being dropped on TMOUS with CM10.
So, I have tried to find out my info, but even when I do; it seems to take me to another path of more information. Hence further confusion.
This is not really a question per se, just wanted to show how I followed several paths; and still confused .
I know one of my biggest issues, is not using the search but inputting the correct data to get the answer I'm seeking. Which is why, I was all over the place.
I'm sure some reading this post will be Fire,Ready Aim. That's OK...Life's to short. After 2 days of this, I have to ask myself...is it worth it to me to accomplish this? Answer, Yes. So, I'll keep trying, till I have a comfort level of doing everything right the first time.
I guess, even though you have produced some great "Hand holding" tools, tutorials etc; there are still some "dummies"..me, that can still get confused.
I guess it would be like me putting you into the B737 I fly, even though you have a manual that tells you everything, you'll still have questions.
Thanks for allowing me to vent.
b737
PS mods, if you feel this is a waste of space, please delete....and I'll move on.
Click to expand...
Click to collapse
well this is a really big description and briefly you mean you want to root your phone and then s-off while having a good nanroid back then try the CM 10 JB rom right??
the process would go in this order
Unlock Bootloader >> 4EXT Recovery >> SuperUser >> S-OFF >> SuperCID >> ICS Firmware >> any ROM/OTA
you'll find all the stuff and instructions on how to do it in this post Guide for GB to ICS
cheers :good:
Hello everyone. I'm a noob.
I have a Droid X2 and Verizon service. It was running Gingerbread 2.3.5 and version 1.3.418, and up until yesterday I hadn't even rooted it. I followed these instructions for CM10 carefully but apparently made a slight mistake.
I made sure to root properly: Superuser worked perfectly, I had Busybox, NANDroid, and Bootstrap Recovery all working, and the phone worked just like before.
In the tutorial I linked to above, I think I know where I went wrong. I downloaded GAPPS 4.2.2 (funky wording since he said 'latest' and then '4.1.x' , so not the latest) and then CM10 A3. I then went into BSR and installed from the external SD card. GAPPS succeeded, but CM10 did not (Status 7, some kernel disapproval or something). When I booted the phone after that, MultiTouch keyboard couldn't start and so I just froze it with Titanium Backup and used Swype because it was annoying. The next thing I tried came from another xda thread (that I seem to have misplaced) saying that removing the top 2 lines of META-INF/com/google/android/updater-script would make it work. I'm pretty sure this failed similarly to before. I then tried wiping all data (since I had backed it up 3 different ways) and installing CM10. It still didn't work, and when I booted I got to my current state of purgatory.
Now when I boot, it tries to run the initial setup but that crashes (and multitouch keyboard crashes too). I've probably lost root access and currently don't have Titanium Backup or any other method to restore from backup since the programs were wiped. I've been trying to do an SBK factory reset using RSD Lite, but the phone won't go into RSD mode.
At this point I just want a working phone again and I'm not sure what to do.
TL;DR: Used the wrong GAPPS version when installing CM10 A3, decided to wipe all my data and try the install, now I'm stuck in neutral.
I guess the internet lied and gave me the wrong SBK the first time. Setup did work, and it wasn't RSD like I had thought.
I still would like to know what went wrong the first time through, and why it seemed like I wasn't able to overwrite the incorrect GAPPS version I had first installed. Once I saw my mistake I did use the correct version and nothing changed.
Dasoccerguy said:
I guess the internet lied and gave me the wrong SBK the first time. Setup did work, and it wasn't RSD like I had thought.
I still would like to know what went wrong the first time through, and why it seemed like I wasn't able to overwrite the incorrect GAPPS version I had first installed. Once I saw my mistake I did use the correct version and nothing changed.
Click to expand...
Click to collapse
Did you get it working then? Were you running A2 before hand?
Dasoccerguy said:
Hello everyone. I'm a noob.
I have a Droid X2 and Verizon service. It was running Gingerbread 2.3.5 and version 1.3.418, and up until yesterday I hadn't even rooted it. I followed these instructions for CM10 carefully but apparently made a slight mistake.
I made sure to root properly: Superuser worked perfectly, I had Busybox, NANDroid, and Bootstrap Recovery all working, and the phone worked just like before.
In the tutorial I linked to above, I think I know where I went wrong. I downloaded GAPPS 4.2.2 (funky wording since he said 'latest' and then '4.1.x' , so not the latest) and then CM10 A3. I then went into BSR and installed from the external SD card. GAPPS succeeded, but CM10 did not (Status 7, some kernel disapproval or something). When I booted the phone after that, MultiTouch keyboard couldn't start and so I just froze it with Titanium Backup and used Swype because it was annoying. The next thing I tried came from another xda thread (that I seem to have misplaced) saying that removing the top 2 lines of META-INF/com/google/android/updater-script would make it work. I'm pretty sure this failed similarly to before. I then tried wiping all data (since I had backed it up 3 different ways) and installing CM10. It still didn't work, and when I booted I got to my current state of purgatory.
Now when I boot, it tries to run the initial setup but that crashes (and multitouch keyboard crashes too). I've probably lost root access and currently don't have Titanium Backup or any other method to restore from backup since the programs were wiped. I've been trying to do an SBK factory reset using RSD Lite, but the phone won't go into RSD mode.
At this point I just want a working phone again and I'm not sure what to do.
TL;DR: Used the wrong GAPPS version when installing CM10 A3, decided to wipe all my data and try the install, now I'm stuck in neutral.
Click to expand...
Click to collapse
you state in the beginning that you are on 2.3.5. it is crazy that you were even able to flash cm10. it is made for 2.3.4 . and DZKs OP on cm10 is a bit sketchy in the wording and severly outdated.
there are a few things you need to do in order to get BSR working inside of A3 , as well as needing the GAPPS for 4.1.X and not 4.2.2 this is only cm10 , not 10.1 .
you need to SBF back to 2.3.4 (google EZsbf for droid x2) it is way easier than trying to use rsdlite for a "noob" , and then root. then follow the steps you completed to get where you are now, except use the right gapps.
THEN: (this is not in the OP for cm10 ) , perform THIS : http://forum.xda-developers.com/showpost.php?p=37698274&postcount=1573 in order to get the patched cm7 bootstrap working. DO NOT try to use the regular BSR .
i can try to help as i get back to my computer here and there, but hopefully others pitch in , as i dont have that much time. hope this helped.
Simpsons11 said:
Did you get it working then? Were you running A2 before hand?
Click to expand...
Click to collapse
I got back to 2.3.5 and restored all my apps and data, so I called it a night. Well... the sun had come up, but same idea. Like I said, up until yesterday I had yet to even root the phone, so I was just running the stock version of Android given to me by Verizon.
Lorenzo VonMatterhorn said:
you state in the beginning that you are on 2.3.5. it is crazy that you were even able to flash cm10. it is made for 2.3.4 . and DZKs OP on cm10 is a bit sketchy in the wording and severly outdated.
there are a few things you need to do in order to get BSR working inside of A3 , as well as needing the GAPPS for 4.1.X and not 4.2.2 this is only cm10 , not 10.1 .
you need to SBF back to 2.3.4 (google EZsbf for droid x2) it is way easier than trying to use rsdlite for a "noob" , and then root. then follow the steps you completed to get where you are now, except use the right gapps.
THEN: (this is not in the OP for cm10 ) , perform THIS : http://forum.xda-developers.com/showpost.php?p=37698274&postcount=1573 in order to get the patched cm7 bootstrap working. DO NOT try to use the regular BSR .
i can try to help as i get back to my computer here and there, but hopefully others pitch in , as i dont have that much time. hope this helped.
Click to expand...
Click to collapse
I wasn't able to flash CM10. I was able to flash GAPPS 4.2.2, but then unable to flash GAPPS 4.1.x over that installation.
And is it really that outdated and sketchy? The version of CM10 I was trying to flash was made on January 11, 2013. Correct me if I'm wrong, but Gingerbread 2.3.5 is almost 2 years old now, right? It's surprising that I'd have to go back to the previous version.
I may try out your suggestions later, but 8 hours of fiddling with my phone yesterday wore me out a little (a lot). Thanks!
Dasoccerguy said:
I got back to 2.3.5 and restored all my apps and data, so I called it a night. Well... the sun had come up, but same idea. Like I said, up until yesterday I had yet to even root the phone, so I was just running the stock version of Android given to me by Verizon.
I wasn't able to flash CM10. I was able to flash GAPPS 4.2.2, but then unable to flash GAPPS 4.1.x over that installation.
And is it really that outdated and sketchy? The version of CM10 I was trying to flash was made on January 11, 2013. Correct me if I'm wrong, but Gingerbread 2.3.5 is almost 2 years old now, right? It's surprising that I'd have to go back to the previous version.
I may try out your suggestions later, but 8 hours of fiddling with my phone yesterday wore me out a little (a lot). Thanks!
Click to expand...
Click to collapse
the OP for cm10 hasnt really been updated since alpha 1 . so yeah it is outdated. alpha 2 had a non working wifi module that was never even mentioned in the OP and had to be figured out by the droid x2 community. alpha 3 had the working wifi back in, but did not have the proper Hijack.zip in place in the system files, whereas the old versions did. this was also never mentioned in the OP.
watch this video. it may help.
http://www.youtube.com/watch?v=HJdvyufvYp0
the dude who made this video also has DOZENS of how-to videos for the droid x2 on his channel. just search for it on youtube. (ex: how to sbf droid x2)
sbfing your phone to 2.3.4 , using EZSBF , shouldnt take more than 15 minutes.
2.3.5 re-introduced a lot of issues that we had with 2.3.4, so most devs base their roms around 2.3.4. in fact, there are really only two roms for 2.3.5 worth trying out, Eclipse, and gingerbread phone , 7 and they are both gingerbread. :crying:
if you read up on what needs to be done, the whole process of SBF, ROOT, and flash cm10 THEN gapps, should all take less than an hour, even for someone who is fairly inexperienced.
i wasnt trying to dog DZK's post for cm10. i was only stating that if you follow HIS instructions, it is confusing as hell.
Lorenzo VonMatterhorn said:
the OP for cm10 hasnt really been updated since alpha 1 . so yeah it is outdated. alpha 2 had a non working wifi module that was never even mentioned in the OP and had to be figured out by the droid x2 community. alpha 3 had the working wifi back in, but did not have the proper Hijack.zip in place in the system files, whereas the old versions did. this was also never mentioned in the OP.
watch this video. it may help.
youtubelink
the dude who made this video also has DOZENS of how-to videos for the droid x2 on his channel. just search for it on youtube. (ex: how to sbf droid x2)
sbfing your phone to 2.3.4 , using EZSBF , shouldnt take more than 15 minutes.
2.3.5 re-introduced a lot of issues that we had with 2.3.4, so most devs base their roms around 2.3.4. in fact, there are really only two roms for 2.3.5 worth trying out, Eclipse, and gingerbread phone , 7 and they are both gingerbread. :crying:
if you read up on what needs to be done, the whole process of SBF, ROOT, and flash cm10 THEN gapps, should all take less than an hour, even for someone who is fairly inexperienced.
i wasnt trying to dog DZK's post for cm10. i was only stating that if you follow HIS instructions, it is confusing as hell.
Click to expand...
Click to collapse
Thanks for the link. I remember watching one of his videos yesterday for something, but apparently this was the one I needed! He does have another video on how to SBF back to 2.3.4, so I think I will just go for it right now.
Also yesterday it only took so long because I had to figure out what mess I had gotten myself into before I could figure out how to figure out what to do. This definitely looks like it shouldn't take more than an hour. :good:
I do have one quick question about backups. NANDroid is a full system backup, including the OS, right? And Titanium Backup is for apps and data? Therefore I should be able to restore all of my apps and data into Android 4.2.1 with Titanium, right? I at least know how to get back to 2.3.5 and restore my data if I can't restore it in 4.2.1, but I'd rather not have to go through this process again if I find out that Titanium can't restore everything.
(haha... I couldn't quote you because of the outside link and my 'xda noob' status )
Dasoccerguy said:
Thanks for the link. I remember watching one of his videos yesterday for something, but apparently this was the one I needed! He does have another video on how to SBF back to 2.3.4, so I think I will just go for it right now.
Also yesterday it only took so long because I had to figure out what mess I had gotten myself into before I could figure out how to figure out what to do. This definitely looks like it shouldn't take more than an hour. :good:
I do have one quick question about backups. NANDroid is a full system backup, including the OS, right? And Titanium Backup is for apps and data? Therefore I should be able to restore all of my apps and data into Android 4.2.1 with Titanium, right? I at least know how to get back to 2.3.5 and restore my data if I can't restore it in 4.2.1, but I'd rather not have to go through this process again if I find out that Titanium can't restore everything.
(haha... I couldn't quote you because of the outside link and my 'xda noob' status )
Click to expand...
Click to collapse
a nandroid backs up the OS as well as all apps and data, but that only helps you if you are modding/messing with that specific rom. so yes, TB is the way to go for restoring apps across roms. glad to point you in the right direction! report back once youve made the jump. :fingers-crossed:
Success!
I used Tomsgt123's tutorials and they were fantastic. First I had to install the 2.3.4 SBK and then CM10 and Gapps. I'm currently running Titanium Backup and it's working flawlessly.
I did have one hiccup earlier though. I noticed that my contacts weren't backed up, and apparently I had disabled the online contact backup also. I was hoping that I could do a NANDroid restore, backup my contacts, and then go through with the CyanogenMod installation. But, the restore kept hanging and refused to finish. I tried 3 or 4 times, and on the last try I restored by section and it was the data section that caused the hang.
So, I'll have to rebuild my contacts list a little bit, but since SMS was backed up I'll at least get the people I care about . Cyanogen is pretty sleek and so far it's been noticeably faster than Gingerbread. I was constantly getting a low framerate just navigating my mainscreen before, and that's one of the reasons I was inspired to try out Jellybean or just anything newer. I can't make any claims about battery life yet since I haven't unplugged it, but other reviews said the battery can last more than twice as long which is fantastic.
I can't thank you enough, Lorenzo, for pointing me in the right direction. :highfive:
Dasoccerguy said:
Success!
I used Tomsgt123's tutorials and they were fantastic. First I had to install the 2.3.4 SBK and then CM10 and Gapps. I'm currently running Titanium Backup and it's working flawlessly.
I did have one hiccup earlier though. I noticed that my contacts weren't backed up, and apparently I had disabled the online contact backup also. I was hoping that I could do a NANDroid restore, backup my contacts, and then go through with the CyanogenMod installation. But, the restore kept hanging and refused to finish. I tried 3 or 4 times, and on the last try I restored by section and it was the data section that caused the hang.
So, I'll have to rebuild my contacts list a little bit, but since SMS was backed up I'll at least get the people I care about . Cyanogen is pretty sleek and so far it's been noticeably faster than Gingerbread. I was constantly getting a low framerate just navigating my mainscreen before, and that's one of the reasons I was inspired to try out Jellybean or just anything newer. I can't make any claims about battery life yet since I haven't unplugged it, but other reviews said the battery can last more than twice as long which is fantastic.
I can't thank you enough, Lorenzo, for pointing me in the right direction. :highfive:
Click to expand...
Click to collapse
thats awesome. i loved the feeling when i first flashed a new rom on this phone. glad you got it figured out. make sure to thank Tomsgt for his videos as well . hes a cool dude and put a lot of time into it.
as for battery life, its kinda a bit rough on cm10. i wouldnt say twice as good. that would be too good to be true...lol . but if you limit your apps, it shouldnt be that much worse.
one thing, to improve performance, under settings, go to developer options, and near the bottom there is background processes. its set at standard limit by default. change it to three at most. this will make a noticeable improvement in performance, but will also need to be re-set at 3 at most if you ever reboot/power off.
glad i could help! :highfive:
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.
I rooted my sprint Note 3 when I first got it three years ago and flashed it with a custom ROM. I used it for a year and then got a cell phone from work, so I basically stopped using the Note 3 except occasionally. I decided the other day that I wanted to try updating to a newer version of android on the Note 3. It's been a long time since I messed around with rooting, ROMs, and such, and I did not pay close attention to what I was doing and flashed a ROM that was incompatible. When I restarted, I got a Set Warranty Bit Kernel error. I can get the phone into download mode, but I'm unsure of what to do next to get it back to a usable state.
Is there a guide somewhere to walk me through this process?
Thanks!
Solved
Well, I got the phone working again. I basically followed this guide I found. I tried to paste in the link but I'm still too much of a noob. Anyway, it was on android central, and part of the url was how-flash-stock-rom-via-odin-new-interface. Hope that helps someone.
There was one step not covered in that guide - odin kept saying that the md5 value was invalid. I found a youtube video that said to change the extension of the firmware (it was .tar.md5, changed to .tar). After that, it worked and my phone is back.
Is there a guide somewhere to walk me through this process?
Click to expand...
Click to collapse
There's guides everywhere on this site! Just gotta find the right ones lol. Makes it that much better when you finally find em. Next time make a complete backup of your phone first. I like to use TWRP, you can download it directly from the Play Store. I got my Stock Firmware from this archive:
http://samsung-updates.com/device/?id=SM-N900P
Make a backup of that then flash away! It'll be a lot easier/faster to recover with TWRP. What ROM did you flash to yours? Just curious cause every one I've tried had multiple issues to where I wasn't even able to use half my phone smh. Then I root it with CF-Auto:
https://forum.xda-developers.com/showthread.php?t=2466423
Through Odin:
http://odindownload.com/download/#.WYX1A4jyuyJ
Then I make a another separate TWRP backup of my Rooted Stock Phone just in case lol. Lemme know if you run into problems again I'll try to help find it and/or fix it. The more problems I deal with the more I learn! :fingers-crossed:
Might wanna get a USB storage or something too cause ALL these backups take up time and space. (My external SD Card slot hasn't worked for awhile!)... does yours?