Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
iArtisan said:
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
Click to expand...
Click to collapse
You should get it. But if any system files are changed by root, the OTA will not install. Otherwise, you should be good to go.
BTW, the Dev Edition 4.4.3 ROM is already posted in Development.
iArtisan said:
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
Click to expand...
Click to collapse
What ROM were you running and how did you get back to stock? I'm stuck on ARHD 10.1 and can't get back to stock
noobsquared said:
What ROM were you running and how did you get back to stock? I'm stuck on ARHD 10.1 and can't get back to stock
Click to expand...
Click to collapse
He probably made a nandroid backup of his stock rom so that he could always go back to stock in cases like this.
You could technically use someone else stock nandroid as well just as long as all the numbers match up. I believe there was a thread here on that.
---------- Post added at 02:13 AM ---------- Previous post was at 02:08 AM ----------
iArtisan said:
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
Click to expand...
Click to collapse
Make sure you restore all the bloatware as well or it won't update. I found this out with the last update. I would hold off on the update until you know it's safe to proceed without losing root unless you want to confirm it first for us. [emoji16]
noobsquared said:
What ROM were you running and how did you get back to stock? I'm stuck on ARHD 10.1 and can't get back to stock
Click to expand...
Click to collapse
What do you mean when you say you "can't get back to stock". What did you try and what was the result?
You can just flash a stock rooted ROM, a stock nandroid (as previously suggested) or run the 1.58 RUU.
volcalstone said:
He probably made a nandroid backup of his stock rom so that he could always go back to stock in cases like this.
You could technically use someone else stock nandroid as well just as long as all the numbers match up. I believe there was a thread here on that.
Click to expand...
Click to collapse
redpoint73 said:
What do you mean when you say you "can't get back to stock". What did you try and what was the result?
You can just flash a stock rooted ROM, a stock nandroid (as previously suggested) or run the 1.58 RUU.
Click to expand...
Click to collapse
I got this nandroid (1.12.502.18 - TWRP 2.6.3.3 Thanks to Wonders_Never_Cease) from http://forum.xda-developers.com/showthread.php?t=2701376 and tried to restore, it ends abruptly leaving wifi and boot screen broken. Phone still boots in ARHD 10.1 but doesn' work perfectly. I put the folder from rar file under TWRP Backup folder and it picked up fine but won't restore. Maybe because I have TWRP 2.7.1.0?
I just picked up the phone and it is S-ON with bootloader unlocked/tempered. I'm trying to get back to stock till we have RUU to convert it to DE eventually like the M7.
I was not able to download the RUU EXE file since it keeps ending abruptly like others suggested. I also tried the HBOOT no PC required version of RUU but it would end abruptly at parsing. Maybe because I'm S-ON? I checked the MID and CID, they are both AT&T stock.
Try flashing a stock rooted ROM from my Index (under CUSTOM ROMs): http://forum.xda-developers.com/showthread.php?t=2751432
noobsquared said:
I was not able to download the RUU EXE file since it keeps ending abruptly like others suggested.
Click to expand...
Click to collapse
I know lots of folks have been having this problem. One guy was going to post a mirror of the RUU, so you might see if he got around to that.
But honestly, the OTA isn't rolling out yet, so why bother at this point? I would just reflash Viper and get your phone fully working again and worry about the OTA later.
And why bother with the OTA at all, or wait for it to roll out? There are already 4.4.3 custom ROMs available. And there is also an AT&T version specific ROM based on the 4.4.4 Dev Edition RUU: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
The AT&T "official" OTA will probably have little if anything different from the DE ROM, aside from all of AT&T's crappy bloatware apps.
redpoint73 said:
Try flashing a stock rooted ROM from my Index (under CUSTOM ROMs): http://forum.xda-developers.com/showthread.php?t=2751432
I know lots of folks have been having this problem. One guy was going to post a mirror of the RUU, so you might see if he got around to that.
But honestly, the OTA isn't rolling out yet, so why bother at this point? I would just reflash Viper and get your phone fully working again and worry about the OTA later.
And why bother with the OTA at all, or wait for it to roll out? There are already 4.4.3 custom ROMs available. And there is also an AT&T version specific ROM based on the 4.4.4 Dev Edition RUU: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
The AT&T "official" OTA will probably have little if anything different from the DE ROM, aside from all of AT&T's crappy bloatware apps.
Click to expand...
Click to collapse
Thanks for the links and everything man but the whole reason I'm trying to go back to completely stock is that I feel there is something wrong with my phone or maybe this is normal for M8. When I flash ARHD 10.1 and click on finish installation, screen gets back to TWRP but then it goes dark for around 2 minutes. I thought it was dead but it finally lit back up and let me restart the phone. Tap on restart and it took a minute. First boot took well over 5 minutes. Been working fine since but I'm not sure why it sometime just sits there with screen off and pimps on it's own. I may try the full AT&T 4.4.3 ROM since it's very close to stock. If I update firmware, can I not go back to stock nandroid? Which I can't anyways but just wondering.
noobsquared said:
When I flash ARHD 10.1 and click on finish installation, screen gets back to TWRP but then it goes dark for around 2 minutes. I thought it was dead but it finally lit back up and let me restart the phone.
Click to expand...
Click to collapse
So after the ROM fully installs (progress bar fills up) and you click "Finish" in AROMA, the screen goes blank for 2 minutes? I haven't seen that. But it might be a ARDH anomaly (I've never flashed it).
noobsquared said:
First boot took well over 5 minutes.
Click to expand...
Click to collapse
Totally normal on the first boot after any ROM flash.
noobsquared said:
Been working fine since but I'm not sure why it sometime just sits there with screen off and pimps on it's own.
Click to expand...
Click to collapse
Ummm, not sure what is being said here "pimp on it's own". I'm guessing a typo or darned auto correct!
noobsquared said:
If I update firmware, can I not go back to stock nandroid? Which I can't anyways but just wondering.
Click to expand...
Click to collapse
I would highly recommend updating firmware if anything is acting buggy on a 2.22 base ROM.
You should be able to restore a nandroid fine with updated firmware. Only thing, is if the nandroid was based on a 1.XX ROM and doesn't play well with the new firmware, you may need to downgrade the firmware.
But honestly, things tend to be always moving forward firmware-wise. It won't be long until all custom ROMs are based on 2.XX, and the 1.XX base wil become obsolete; with most folks being on the newer firmware and few (if any) reasons to go back or be on old firmware.
redpoint73 said:
So after the ROM fully installs (progress bar fills up) and you click "Finish" in AROMA, the screen goes blank for 2 minutes? I haven't seen that. But it might be a ARDH anomaly (I've never flashed it).
I would highly recommend updating firmware if anything is acting buggy on a 2.22 base ROM.
You should be able to restore a nandroid fine with updated firmware. Only thing, is if the nandroid was based on a 1.XX ROM and doesn't play well with the new firmware, you may need to downgrade the firmware.
But honestly, things tend to be always moving forward firmware-wise. It won't be long until all custom ROMs are based on 2.XX, and the 1.XX base wil become obsolete; with most folks being on the newer firmware and few (if any) reasons to go back or be on old firmware.
Click to expand...
Click to collapse
Yes, once the rom is installed, it exits out to TWRP, I get a flash of TWRP screen and then it goes dark. I press power button and wait for 2 minutes for it to come back on. I'm tempted to just convert it to Dev Edition but with all the issues people are having with phones these days, I want to make sure I can get it fixed under warranty or something if hardware craps out.
I am not even able to restore the nandroid for AT&T at this point. TWRP starts restoring nandroid and then goes back to TWRP main screen and the ARHD rom becomes very buggy (wifi won't turn on, gets super slow, developer warning on boot screen goes away, etc.)
I will try to update the firmware and try to get on that AT&T Rom bandwagon to see how it goes. Thanks for all your help and input. I wish it wasn't so complicated with M8. M7 was so easy to mess with or maybe I got used to that lol
noobsquared said:
I am not even able to restore the nandroid for AT&T at this point. TWRP starts restoring nandroid and then goes back to TWRP main screen and the ARHD rom becomes very buggy (wifi won't turn on, gets super slow, developer warning on boot screen goes away, etc.)
Click to expand...
Click to collapse
After a aborted TWRP restore, I'm actually surprised to see the formerly installed ROM (I think that is what you are saying) to boot at all. Wipe and reflash ARHD.
Broken WiFi is a known issue with the 2.22 based ROMs + outdated firmware. Not sure about the other issues, but updating the firmware and reflashing ARHD might do the trick.
noobsquared said:
Yes, once the rom is installed, it exits out to TWRP, I get a flash of TWRP screen and then it goes dark. I press power button and wait for 2 minutes for it to come back on.
Click to expand...
Click to collapse
That's odd. Did this only happen once, or can your reproduce this bug? Any mention of this on the ARHD thread?
You might also try to wipe cache and re-install TWRP. Could just be a bad TWRP install.
noobsquared said:
I'm tempted to just convert it to Dev Edition but with all the issues people are having with phones these days, I want to make sure I can get it fixed under warranty or something if hardware craps out.
Click to expand...
Click to collapse
FYI, as long as you are a current account holder, AT&T doesn't give a darn what you change in software, they will still honor the warranty if there is a hardware issue.
redpoint73 said:
After a aborted TWRP restore, I'm actually surprised to see the formerly installed ROM (I think that is what you are saying) to boot at all. Wipe and reflash ARHD.
Broken WiFi is a known issue with the 2.22 based ROMs + outdated firmware. Not sure about the other issues, but updating the firmware and reflashing ARHD might do the trick.
That's odd. Did this only happen once, or can your reproduce this bug? Any mention of this on the ARHD thread?
You might also try to wipe cache and re-install TWRP. Could just be a bad TWRP install.
Click to expand...
Click to collapse
Thanks for the information on hardware warranty. I hope it never comes to that.
I actually installed ARHD twice or 3 times last night since every attempt to go back to AT&T stock failed and I had a half working jacked up device. I went in TWRP, re-installed ARHD and everything was good to go. Every time I installed the ROM, I had to wait a couple minutes to hit reboot after ROM installation since TWRP would take a nap. I'm not too worried about it since everything seems to be working fine but it's still kinda bothersome, you know?
At this point in time, everything is running well on ARHD 10.1 so I guess I will take a chill pill.
Thanks once again for all your help
noobsquared said:
Thanks for the information on hardware warranty. I hope it never comes to that.
I actually installed ARHD twice or 3 times last night since every attempt to go back to AT&T stock failed and I had a half working jacked up device. I went in TWRP, re-installed ARHD and everything was good to go. Every time I installed the ROM, I had to wait a couple minutes to hit reboot after ROM installation since TWRP would take a nap. I'm not too worried about it since everything seems to be working fine but it's still kinda bothersome, you know?
At this point in time, everything is running well on ARHD 10.1 so I guess I will take a chill pill.
Thanks once again for all your help
Click to expand...
Click to collapse
Just an FYI- the black screen is a common problem with aroma installers and is well known.. All the other issues? I haven't a clue.
Hello!
I'm using 2.22 WWE version stock rom with 4.4.3, but I have long boots of device with old AT&T firmware.
Is there any way to update firmware?
I'm s-on, and firewater doesn't works.
noobsquared said:
Thanks for the information on hardware warranty. I hope it never comes to that.
I actually installed ARHD twice or 3 times last night since every attempt to go back to AT&T stock failed and I had a half working jacked up device. I went in TWRP, re-installed ARHD and everything was good to go. Every time I installed the ROM, I had to wait a couple minutes to hit reboot after ROM installation since TWRP would take a nap. I'm not too worried about it since everything seems to be working fine but it's still kinda bothersome, you know?
At this point in time, everything is running well on ARHD 10.1 so I guess I will take a chill pill.
Thanks once again for all your help
Click to expand...
Click to collapse
OP here.
The black screen you're getting is due to TWRP timing out. You can turn that off in the settings. This is a non-issue though and nothing to worry about.
The long boot times, however, is a problem. This is happening because you're on the old AT&T firmware. Unfortunately, there's no way to flash the latest firmware without S-OFF. Your only option is to return to stock and wait for the official 4.4.3 OTA. Flash a nandroid backup (I'll send you a link to the one I used later, or just search around for the master list here.) through TWRP and then flash stock recovery through fastboot. Let me know if you need detailed instructions on how to do this.
Thanks guys for all the help and support. I messed with the phone quite a bit and tried quite a few things and all the posts here help me learn a lot too. I was able to go all stock after s-off using that RUU method. I tried a couple other roms and finally back to dev edition stock for now. Was able to convert completely to stock with all the info and so far so good.
Once again, thanks a bunch everyone
Sent from my HTC One_M8 using XDA Free mobile app
iArtisan said:
OP here.
The black screen you're getting is due to TWRP timing out. You can turn that off in the settings. This is a non-issue though and nothing to worry about.
The long boot times, however, is a problem. This is happening because you're on the old AT&T firmware. Unfortunately, there's no way to flash the latest firmware without S-OFF. Your only option is to return to stock and wait for the official 4.4.3 OTA. Flash a nandroid backup (I'll send you a link to the one I used later, or just search around for the master list here.) through TWRP and then flash stock recovery through fastboot. Let me know if you need detailed instructions on how to do this.
Click to expand...
Click to collapse
I bit the bullet and just paid $25 for SunShine so I could get S-OFF and update the firmware
http://forum.xda-developers.com/showthread.php?t=2792487
cachookaman said:
I bit the bullet and just paid $25 for SunShine so I could get S-OFF and update the firmware
http://forum.xda-developers.com/showthread.php?t=2792487
Click to expand...
Click to collapse
I had to do the same thing but given that what a pain it is without s-off, I'm not complaining. $25 is a small fee to pay for the peace of mind that you ha e almost full control of the device now.
Sent from my HTC One_M8 using XDA Free mobile app
Related
Before I do anything else to screw this up!
I'm sitting at an exclamation in a triangle
here what I did..
1. installed stock/rooted rom
2. used clean flash to put on stock recovery
3. ran OTA Keeper to back up root
4. downloaded and started OTA update
it then rebooted and began but then Red Exclamation In A Triangle
anyone know where I should go or what I should do from here?
Thanks.
If your pc detects the phone- you'll prob have to do an ruu.exe to get it totally stock and then start over.. I did it earlier but I was having a diff problem (stuck in hboot)-- never got triangle/exclamation. I used the ruu from scottsroms (1.02.605.6).
yeah ok... I'll look into that. I haven't turned it back on yet.. Thanks
Just realized i forgot to "un-root" with the OTAKeeper app... I'm hoping that's what I did wrong. It booted back to where i was and said the update failed. So... I'm a tryin' again.
Thanks for the reply.. One can feel soooo alone when making mistakes
There's some other information in the OTA threads in "general" of others that have had the red triangle and were able to work around it.. I didn't read the specifics but check in there.
das0527 said:
7. Enjoy OTAed, unlocked, rooted kickassness of my Rezound while bouncing off the walls waiting for ICS.
Click to expand...
Click to collapse
Why wait?
I'm going to run through those steps later and check out the other threads. I'm able to get back to my phone as the update looks to of just been aborted....
If you guys don't have wives, keep it that way, I want to work on this all day but...... so I'll check in later and post how it goes. I don't see why those steps won't work though... Thanks a ton guys.
I planned on waiting until the official build of ICS & Sense is released OTA, especially after today's news about the new features in Sense 4.0, which I'm actually extremely impressed with.
Cool- well I'm sure you've already read elsewhere- but you can't really go wrong w/ any of the custom ics roms in the dev section. If you can handle a very occasional screen flicker every once in a while they're pretty much perfect.
reggie cheeks said:
Before I do anything else to screw this up!
I'm sitting at an exclamation in a triangle
here what I did..
1. installed stock/rooted rom
2. used clean flash to put on stock recovery
3. ran OTA Keeper to back up root
4. downloaded and started OTA update
it then rebooted and began but then Red Exclamation In A Triangle
anyone know where I should go or what I should do from here?
Thanks.
Click to expand...
Click to collapse
Did you lock the bootloader?
Sent from my ADR6425LVW using xda premium
No. I didn't. That was my mistake. Dumb of me. I'm gonna do the ruu and start over later, I'm out n about.
Sent from my ADR6425LVW using Tapatalk
Why lock the bootloader? There are a bunch of us who were able to successfully OTA without doing so. My radios are all updated as well as the OS. If you debloated, you need to reenable the bloat prior. No need to unroot either.
esheesle said:
Why lock the bootloader? There are a bunch of us who were able to successfully OTA without doing so. My radios are all updated as well as the OS. If you debloated, you need to reenable the bloat prior. No need to unroot either.
Click to expand...
Click to collapse
Had Ineffabilis from 12/29, was great, put Clean ICS on it from 1/24, worked well except for the bluetooth pain in the patookie. (and I use bluetooth ALOT)...
I flashed back to GB, I have Team Bamf on mine right now because it included the kernel. I am getting ready to put clean rom on it with the new main ver but I would like to put the new radio's on it first.
Can I put the new radio's on it without going through the steps above (flash stock, re lock, ruu, ota update, unlock, flash, etc) and if so how?
Thanks!
Figured it out. Gonna make a post.
esheesle said:
Why lock the bootloader? There are a bunch of us who were able to successfully OTA without doing so. My radios are all updated as well as the OS. If you debloated, you need to reenable the bloat prior. No need to unroot either.
Click to expand...
Click to collapse
Right now I'm on Vigor Stock Rooted WWE 1.02.605.6 Deodexed . That's my mistake, right? I've got all the bloat.
Sent from my ADR6425LVW using Tapatalk
It's possible the deodexed part of it is the problem.
Do you have a nandroid made from right after you flashed Amon Ra recovery? Also, did you flash a stock recovery or do you still have Amon Ra? It won't work unless you have stock recovery.
If you don't have a nand, you can either run RUU (if you don't have the updated mainver issue) or have a look in this thread:
http://forum.xda-developers.com/showthread.php?t=1467329
con247 has made a stock ROM with the OTA in it so you don't have to download the update.
There aren't any instructions on what to do with the file you download and I didn't use his method so I can't really help but hopefully you'll get it. I don't remember it being spelled out in the thread anywhere which is why I decided it was just as easy for me to use my nand and flash a stock kernel and recovery and download it myself.
I had stock recovery and kernel at the time I ran the update. I've since went back to amon and I've downloaded vigor ota stock rooted and I was about to try that.
Oh and...I'm pretty sure my earliest back up was not my original, I think I made the mistake of flashing a Rom before my first backup
I do however really wish I had some instructions for the vigorotastockrooted.
& one last thing.. Ive never had mainver update.
Sent from my ADR6425LVW using Tapatalk
Yeah, I wish there were instructions for that stock + OTA too.
The OTA will update your mainver but to the official release that is in the OTA. Just so you know, I can now not flash the dbs kernel I was using before because I'm getting a "mainver is older" message.
I was trying to reflash kernels because my wifi is not working now, when I select "turn on wifi" that changes to "error". I had restored my nand of the Innedfabilis ROM I made right before reverting to stock and updating with the OTA. Just mentioning it since I'm posting here to try to help you and I guess it's just full disclosure.
Hmm. I'm thinking of sticking pre-ota as well, at least until I feel more confident about it. Thanks
Edit.... I ended up using con's vigorOta and xtreme tools (for simpler lock/relock) to update . Thanks for the help/insight!
Sent from my ADR6425LVW using Tapatalk
A couple weeks ago, I decided it was time to root my phone, since I missed running the custom ROMs on my Droid. So I unlocked it and rooted it and everything went all fine and dandy. I decided for my first ROM, I would flash Xtreme Outcast's ICS ROM (v2.0, I think). When I first flashed it, my data worked fine (however downloading apps from the market gave me some issues, but I think that was another problem..). However, before long, like later that day, the 4g and 3g stopped working. After it stopped working, I decided to try to restore my nandroid stock ROM, but when I went back to it, not only did the 4g and 3g not work, the wifi just said 'error' when I tried to turn it on. So after that, I tried to flash the GB OTA RUU, but that gave me some issues, but I've figured out where that went wrong (mainver error).
Anyway, what I'm trying to figure out is what I can do to try to fix the issue. My mobile data IS on, the battery cover IS on, and the SIM card is inserted and, to my knowledge, working just fine. Would flashing an RUU help? Am I just having bad luck with this ROM and need to flash a different one? Should I update to the new RUU? Any help would be fantastic, and I'd award you 456789876435974 awesome points!
Sounds like you may have had a bad ROM zip. I would try re-downloading the ROM and re-flashing making sure you wipe all/factory reset first. If that works and you are feeling adventurous, I highly recommend Scott's ROMs new CleanRom 4.1 which requires an RUU. Check out his web site and developer thread here for more info. I took the leap and love it.
woodyt74 said:
Sounds like you may have had a bad ROM zip. I would try re-downloading the ROM and re-flashing making sure you wipe all/factory reset first. If that works and you are feeling adventurous, I highly recommend Scott's ROMs new CleanRom 4.1 which requires an RUU. Check out his web site and developer thread here for more info. I took the leap and love it.
Click to expand...
Click to collapse
Thanks for the response, but do you think it was just a bad flash if it affected the stock nandroid backup too? I will try flashing a new ROM soon either way, though. Is it possible to download an older version of CleanRom? I can't find a link on the first page of the thread, though I might have just overlooked it. I'm just not sure if I want to update to the new RUU right now, but if there are no other options, I might just pull the trigger on it.
Go to Scott's ROMs web site and you can download ISCE 3.7 which is still on the old firmware so no RUU needed. His roms are pretty slick and he provides great support.
Good point on the nandroid so I'm not sure what's going on. Hopefully the new ROM flash helps.
Well, I flashed the ICS RUU, and now my data works! but now...I can't get my phone to root. Is there a guide for rooting on the new RUU?
CollinswithanS said:
Well, I flashed the ICS RUU, and now my data works! but now...I can't get my phone to root. Is there a guide for rooting on the new RUU?
Click to expand...
Click to collapse
It is just easiest to install and ICS new firmware ROM that is already rooted.
There is however a couple of thread in the development forum on rooting and there is an ICS root tool there
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Bump in hopes of someone's experience or advice.
falkon114 said:
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Click to expand...
Click to collapse
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
*see below*
Jiggabitties said:
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
Click to expand...
Click to collapse
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
falkon114 said:
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
Click to expand...
Click to collapse
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Jiggabitties said:
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Click to expand...
Click to collapse
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
falkon114 said:
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
Click to expand...
Click to collapse
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Jiggabitties said:
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Click to expand...
Click to collapse
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
falkon114 said:
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
Click to expand...
Click to collapse
Glad I could help in any way. Bummer about your camera.
Hey guys,
Yesterday I tried to update my ViperOne from 2.5 to 3.2 and being the dumbass that I am, I didn't read the note saying my wifi wouldn't work unless I have 4.4.4
It installed fine but I wanted to go back so I followed Viper's guide on reverting to another version. After hours of dicking around, my phone got stuck on the white htc screen. I did power + vol up and got to the recovery menu and remembered that I had a backup of my stock firmware. Lesson learned (always make backups)
Anyways, i booted into the back up image and now everything is working.
My question is, is my phone ok? After the white screen I'm kinda scared I might've ****ed something up. If it's working then I don't have to worry about anything, correct?
Thanks for your help!
XtremelyNooby said:
Hey guys,
Yesterday I tried to update my ViperOne from 2.5 to 3.2 and being the dumbass that I am, I didn't read the note saying my wifi wouldn't work unless I have 4.4.4
It installed fine but I wanted to go back so I followed Viper's guide on reverting to another version. After hours of dicking around, my phone got stuck on the white htc screen. I did power + vol up and got to the recovery menu and remembered that I had a backup of my stock firmware. Lesson learned (always make backups)
Anyways, i booted into the back up image and now everything is working.
My question is, is my phone ok? After the white screen I'm kinda scared I might've ****ed something up. If it's working then I don't have to worry about anything, correct?
Thanks for your help!
Click to expand...
Click to collapse
Nice to know you at least had a backup. You didn't mess anything up you just needed to update your firmware for it to work without any above mentioned issues.
Have you read about S-OFF?
Are you S-OFF?
jball said:
Nice to know you at least had a backup. You didn't mess anything up you just needed to update your firmware for it to work without any above mentioned issues.
Have you read about S-OFF?
Are you S-OFF?
Click to expand...
Click to collapse
I've read about S-OFF
I am S-On
XtremelyNooby said:
I've read about S-OFF
I am S-On
Click to expand...
Click to collapse
You need s-off to update firmware. Once you have s-off, then the firmware I would recommend for use on AT&T's network is 3.28.1540, which is posted on the ROM thread here: http://forum.xda-developers.com/att-htc-one-m8/development
Otherwise, your other option is to return to full stock ROM and stock recovery and install the official 4.4.4 OTA once it rolls out from AT&T (rumored mid-December) which will automatically update the firmware. After the OTA, you will then need to re-install custom recovery, to flash a custom ROM.
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.